Hello Eric,
* Eric Blake wrote on Mon, Aug 23, 2010 at 11:59:04PM CEST:
> Meanwhile, I don't see how warning on unexpected arguments is a
> problem - code that wants to be portable to both old and new
> autoconf will only use as many arguments as the old version
> supported.
Or try to use the new
Hi Patrick,
* Patrick Welche wrote on Tue, Aug 24, 2010 at 05:33:18PM CEST:
> On Tue, Aug 24, 2010 at 09:19:31AM -0600, Eric Blake wrote:
> > On 08/24/2010 08:08 AM, Patrick Welche wrote:
> > >Highlight (NetBSD-current/i386, autoconf head) is:
> > >
> > >./torture.at:1223: cd $dir&& $MAKE
> > >st
On Tue, Aug 24, 2010 at 09:19:31AM -0600, Eric Blake wrote:
> On 08/24/2010 08:08 AM, Patrick Welche wrote:
> >Highlight (NetBSD-current/i386, autoconf head) is:
> >
> >./torture.at:1223: cd $dir&& $MAKE
> >stderr:
> >make: don't know how to make w. Stop
> >stdout:
Curious: the above was from the
On 08/24/2010 08:08 AM, Patrick Welche wrote:
Highlight (NetBSD-current/i386, autoconf head) is:
./torture.at:1223: cd $dir&& $MAKE
stderr:
make: don't know how to make w. Stop
stdout:
This output is not from GNU make. VPATH builds with other makes are
likely to trigger bugs in those make i
Highlight (NetBSD-current/i386, autoconf head) is:
./torture.at:1223: cd $dir && $MAKE
stderr:
make: don't know how to make w. Stop
stdout:
make: stopped in /usr/src/local/autoconf/tests/testsuite.dir/240/at
./torture.at:1223: exit code was 2, expected 0
But I find it hard to start debugging as
В Mon, 23 Aug 2010 11:01:14 -0700, Paul Eggert написа:
> On 08/23/10 10:28, John Calcote wrote:
>> What is the correct approach for this situation? Should I simply define
>> __USE_UNIX98 in my source code
>
> No, because that symbol is private to glibc. I wouldn't mess with it.
> Instead, use Aut
