Subject: Re: Error code 1 without real error message
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 09/27/2003 23:09:50
[ On Saturday, September 27, 2003 at 19:30:35 (-0700), Jeremy C. Reed wrote: ]
> Subject: Re: Error code 1 without real error message
> On Sat, 27 Sep 2003, Greg A. Woods wrote:
> > (and why do you use "echo something | sed 's,.*/,,'" instead of basename? :-)
> That was from the original bc distfile Makefile.in.
Ah..... so I wonder why the original author failed to use such a common
and simple built-in command? :-)
> I didn't provide much information, because I recall reading that something
> changed in how bmake reported errors. I read several messages about it. I
> wanted to know more about it -- and answers to my original questions.
Well if you check the list archives you'll find that the only thing that
was to be changed was the content of the "Error code 1" message itself;
and the change, as I understand it, is/was only supposed to show the
command that failed, yet the example you showed you didn't include
anything like the examples used in the discussion about those changes
which leads me to believe that you're not actually running a newer
version of "make" which might include those changes.
In any case nothing should have been done to redirect output from any of
the commands "make" runs. If you're not seeing output from the
"makeinfo" command then that must be because the rules which have caused
it to be executed also include something which is causing its output to
be redirected. Use of PKG_DEBUG_LEVEL=2 should have revealed to you why
you were not seeing the output, assuming you can spot all the possible
subtle shell syntax which might cause it to fail to appear on your tty.
Greg A. Woods
+1 416 218-0098 VE3TCP RoboHack <firstname.lastname@example.org>
Planix, Inc. <email@example.com> Secrets of the Weird <firstname.lastname@example.org>