libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: branch-2-0 tests: linux-dietlibc


From: Ralf Wildenhues
Subject: Re: branch-2-0 tests: linux-dietlibc
Date: Tue, 23 Nov 2004 11:08:53 +0100
User-agent: Mutt/1.4.1i

* Gary V. Vaughan wrote on Fri, Nov 19, 2004 at 04:40:00AM CET:
> Ralf Wildenhues wrote:
> 
> >                           The f77demo configure script breaks
> >spectacularly by outputting its own contents after
> >| configure: error: linking to Fortran libraries from C fails
> >
> >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.

Regards,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]