[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: branch-2-0 tests: linux-dietlibc
From: |
Gary V. Vaughan |
Subject: |
Re: branch-2-0 tests: linux-dietlibc |
Date: |
Tue, 23 Nov 2004 11:29:42 +0000 |
User-agent: |
Mozilla Thunderbird 0.9 (X11/20041103) |
Hallo Ralf,
Ralf Wildenhues wrote:
> * Gary V. Vaughan wrote on Fri, Nov 19, 2004 at 04:40:00AM CET:
>
> > Ralf Wildenhues wrote:
> > > Any hints as to where I should start looking?
> >
> > Usually that means that either ECHO is screwed up and the reexec ends up
> > sending configure to stdout rather than doing fallback echo, or else
> > there could be a bug in one of the $0 expansions getting done wrong, or
> > maybe a sed command is doing the wrong thing.
>
>
> Nope. That's just what func_configure does: From defs.m4sh:
>
> | eval func_msg $SHELL "$my_testdir/configure" $my_args
> | eval $SHELL "$my_testdir/configure" $my_args || \
> | { func_msg "FAILED: Configuring in $my_testdir"
> | ls -ltr $my_testdir
> | eval $SHELL -vx "$my_testdir/configure" $my_args;
> | exit $EXIT_FAILURE;
> | }
>
> The verbose output was added with
>
> | 2003-11-24 Gary V. Vaughan <address@hidden>
> |
> | * tests/defs (func_configure): cdemo, demo and mdemo are shows
> | signs of indeterminacy for some users. Be more verbose during
> | failure to help track down the cause.
>
> Should we leave it in? It confused the heck out of me at least.
> If we leave it in, I suggest adding some
> $ECHO "re-running configure with verbose output"
> or such.
It certainly wasn't designed to confuse, so that is a bug! However, since
we are moving to a whole new testsuite, please feel free to make whatever
change you think most useful here.
Cheers,
Gary.
--
Gary V. Vaughan ())_. address@hidden,gnu.org}
Research Scientist ( '/ http://tkd.kicks-ass.net
GNU Hacker / )= http://www.gnu.org/software/libtool
Technical Author `(_~)_ http://sources.redhat.com/autobook
signature.asc
Description: OpenPGP digital signature