[Top][All Lists]

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

Re: testsuite: 24 25 64 failed

From: Ralf Wildenhues
Subject: Re: testsuite: 24 25 64 failed
Date: Mon, 24 Mar 2008 10:56:38 +0100
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

Hello Nix,

Thanks for the testsuite feedback.

* Nix wrote on Fri, Mar 21, 2008 at 08:01:13PM CET:
> The underlying cause of test 24's failure appears to be that LDFLAGS is
> not consistently propagated down: note that a lot of the link steps do
> not pass in my LDFLAGS of -specs=specs.no-as-needed, so get linked with
> --as-needed (which is the default on my system) and subsequently
> fail. (FWIW the only things I've ever seen fail with --as-needed are
> linker-semantics testsuites like this one. :)

First, you can try

to get your flag passed down consistently.  Second, we've had a test
report that consistently used -Wl,--as-needed which only failed the
template subdir test (and that failure is due to a bug in the test).

> Test 25's failure is weirder and I don't know what its cause might be yet.

It looks weird because you have configured 
  --enable-shared --disable-static

but somehow it seems the test fails to properly detect that.
Please post the output of
  make check-local TESTSUITEFLAGS='-v -d -x -k "static linking"'


> Test 64 doesn't seem to have any failure details in the log at all.

Oh it does.  Test 64 reruns a number of the other tests with low
max_cmd_len set, it just sees the failures of 24 and 25 again.


reply via email to

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