anyone know how to shut these ports up?

Julian Elischer julian at freebsd.org
Sat May 26 06:08:05 UTC 2018


several ports, when compiled output a MASS of stuff that looks like:

      No recipe for '../gnulib/m4/stdio_h.m4' and no prerequisites 
actually changed.
      No need to remake target '../gnulib/m4/stdio_h.m4'.
      Considering target file '../gnulib/m4/stdlib_h.m4'.
       Looking for an implicit rule for '../gnulib/m4/stdlib_h.m4'.
       Trying pattern rule with stem 'stdlib_h.m4'.
       Trying implicit prerequisite '../gnulib/m4/stdlib_h.m4,v'.
       Trying pattern rule with stem 'stdlib_h.m4'.
       Trying implicit prerequisite '../gnulib/m4/RCS/stdlib_h.m4,v'.
       Trying pattern rule with stem 'stdlib_h.m4'.
       Trying implicit prerequisite '../gnulib/m4/RCS/stdlib_h.m4'.
       Trying pattern rule with stem 'stdlib_h.m4'.
       Trying implicit prerequisite '../gnulib/m4/s.stdlib_h.m4'.
       Trying pattern rule with stem 'stdlib_h.m4'.
       Trying implicit prerequisite '../gnulib/m4/SCCS/s.stdlib_h.m4'.
       No implicit rule found for '../gnulib/m4/stdlib_h.m4'.
       Finished prerequisites of target file '../gnulib/m4/stdlib_h.m4'.
      No recipe for '../gnulib/m4/stdlib_h.m4' and no prerequisites 
actually changed.
      No need to remake target '../gnulib/m4/stdlib_h.m4'.
      Considering target file '../gnulib/m4/stpcpy.m4'.
       Looking for an implicit rule for '../gnulib/m4/stpcpy.m4'.

...  except for about 20 minutes (my connection to the machine doing 
the work is not that fast)


I suspect print/texinfo is one (it's kind of hard to tell exactly when 
they go off to do dependencies..)

Does anyone know the secret to shutting up all this debug stuff?

It literally pumps out so much crap that the rest of he family gets 
bumped off the internet connection..

(including any other session I may have running)




More information about the freebsd-ports mailing list