From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'Steve Ellcey' <sje@cup.hp.com>,
binutils@sourceware.org, gcc-patches@gcc.gnu.org,
gdb-patches@gcc.gnu.org, newlib@sourceware.org,
Ralf.Wildenhues@gmx.de, aoliva@redhat.com,
libtool@cwilson.fastmail.fm, schwab@suse.de
Subject: Re: Final(?) patch to update libtool in GCC and src trees
Date: Wed, 11 Apr 2007 07:36:00 -0000 [thread overview]
Message-ID: <461C8FE6.9010800@lu.unisi.ch> (raw)
In-Reply-To: <008301c77bd6$7fa44bc0$2e08a8c0@CAM.ARTIMI.COM>
Dave Korn wrote:
> On 10 April 2007 21:07, Steve Ellcey wrote:
>
>>> I appreciate the problem, but Cygwin can be a bit 'special' when it
>>> comes to libtool; if it hasn't been done yet, can you possibly bear to
>>> hold off a bit while I give it some hasty testing? (By 'a bit', I mean no
>>> more than say 'overnight'). Sorry to be a pain :-/
>>>
>>>
>>> cheers,
>>> DaveK
>> I can wait, especially since no one has given me the go ahead yet. :-)
>> I know of no cygwin testing that has been done.
>
> Mixed results so far. Patching a binutils checkout and building it got me
> this:
>
>
> === ld tests ===
> @@ -297,14 +297,8 @@ Running /usr/build/src-binutils/ld/tests
> Running /usr/build/src-binutils/ld/testsuite/ld-arm/arm-elf.exp ...
> Running /usr/build/src-binutils/ld/testsuite/ld-auto-import/auto-import.exp
> ...
> Running /usr/build/src-binutils/ld/testsuite/ld-bootstrap/bootstrap.exp ...
> -FAIL: bootstrap
> -FAIL: bootstrap with strip
> FAIL: bootstrap with --static
> -FAIL: bootstrap with --traditional-format
> -FAIL: bootstrap with --no-keep-memory
> -FAIL: bootstrap with --relax
> Running /usr/build/src-binutils/ld/testsuite/ld-cdtest/cdtest.exp ...
> -FAIL: cdtest
> FAIL: cdtest with -Ur
> Running /usr/build/src-binutils/ld/testsuite/ld-checks/checks.exp ...
> Running /usr/build/src-binutils/ld/testsuite/ld-cris/cris.exp ...
> @@ -396,40 +390,40 @@ Running /usr/build/src-binutils/ld/tests
>
> === ld Summary ===
>
> -# of expected passes 53
> -# of unexpected failures 9
> +# of expected passes 59
> +# of unexpected failures 3
> # of unexpected successes 1
> # of expected failures 3
> # of unsupported tests 1
> -/usr/build/obj-binutils/ld/ld-new 2.17.50.20070410
> +/usr/build/obj-binutils-patched/ld/ld-new 2.17.50.20070410
>
>
> ..which is entirely good :-D Then I tried a winsup checkout; it failed to
> configure in newlib:
>
> checking for i686-pc-cygwin-ranlib... ranlib
> checking for i686-pc-cygwin-readelf... no
> checking for readelf... readelf
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for .preinit_array/.init_array/.fini_array support... readelf: Error:
> Input file 'conftest' is not readable.
> no
> checking for array aliasing support... yes
> configure: updating cache ./config.cache
> configure: error: conditional "am__fastdepCXX" was never defined.
> Usually this means the macro was only invoked conditionally.
> Makefile:8649: *** [configure-target-newlib] Error 1
>
> #0 configure-target-newlib at /usr/build/obj-winsup.new/Makefile:8649
> #1 all-target-newlib at /usr/build/obj-winsup.new/Makefile:8690
> #2 maybe-all-target-newlib at /usr/build/obj-winsup.new/Makefile:8687
> #3 all-target (.PHONY target)
> make[1]: Leaving directory `/usr/build/obj-winsup.new'
>
>
> This is what config.log showed:
>
> configure:3737: checking for a BSD-compatible install
> configure:3793: result: /usr/bin/install -c
> configure:3808: checking whether to enable maintainer-specific portions of
> Makefiles
> configure:3817: result: no
> configure:21892: checking for .preinit_array/.init_array/.fini_array support
> configure:21905: gcc -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup
> -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/cygwin
> -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/w32api/lib -isystem
> /usr/build/src-winsup/winsup/include -isystem
> /usr/build/src-winsup/winsup/cygwin/include -isystem
> /usr/build/src-winsup/winsup/w32api/include
> -B/usr/build/obj-winsup.new/i686-pc-cygwin/newlib/ -isystem
> /usr/build/obj-winsup.new/i686-pc-cygwin/newlib/targ-include -isystem
> /usr/build/src-winsup/newlib/libc/include
> -I/usr/build/src-winsup/winsup/cygwin/include -o conftest conftest.c
> -static -nostartfiles -nostdlib 1>&5
> configure:21908: $? = 0
> configure:21921: result: no
> configure:21931: checking for array aliasing support
> configure:21942: gcc -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup
> -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/cygwin
> -L/usr/build/obj-winsup.new/i686-pc-cygwin/winsup/w32api/lib -isystem
> /usr/build/src-winsup/winsup/include -isystem
> /usr/build/src-winsup/winsup/cygwin/include -isystem
> /usr/build/src-winsup/winsup/w32api/include
> -B/usr/build/obj-winsup.new/i686-pc-cygwin/newlib/ -isystem
> /usr/build/obj-winsup.new/i686-pc-cygwin/newlib/targ-include -isystem
> /usr/build/src-winsup/newlib/libc/include
> -I/usr/build/src-winsup/winsup/cygwin/include -c conftest.c
> 1>&5
> conftest.c:1: warning: excess elements in scalar initializer
> conftest.c:1: warning: (near initialization for `x3')
> conftest.c:1: warning: excess elements in scalar initializer
> conftest.c:1: warning: (near initialization for `x3')
> configure:21945: $? = 0
> configure:21954: result: yes
> configure:22030: updating cache ./config.cache
> configure:22141: error: conditional "am__fastdepCXX" was never defined.
> Usually this means the macro was only invoked conditionally.
>
>
> Note the huge jump:
>
> configure:3817: result: no
> configure:21892: checking for .preinit_array/.init_array/.fini_array support
Right.
Inside those two lines we have
if test "${use_libtool}" = "yes"; then
AC_LIBTOOL_WIN32_DLL
AM_PROG_LIBTOOL
AC_PROG_AWK
fi
I would rewrite them at the very least as
AC_PROG_AWK
AC_PROG_CXX
if test "${use_libtool}" = "yes"; then
AC_LIBTOOL_WIN32_DLL
AM_PROG_LIBTOOL
fi
There might be more macros to put above the "if" to avoid that they be
expanded inside an "if".
Paolo
next prev parent reply other threads:[~2007-04-11 7:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 18:25 Steve Ellcey
2007-04-10 18:42 ` Andrew Pinski
2007-04-10 20:04 ` Steve Ellcey
2007-04-10 20:02 ` Dave Korn
2007-04-10 20:07 ` Steve Ellcey
2007-04-10 20:58 ` Dave Korn
2007-04-11 1:13 ` Dave Korn
2007-04-11 7:36 ` Paolo Bonzini [this message]
2007-04-11 8:47 ` Andreas Schwab
2007-04-11 8:51 ` Paolo Bonzini
2007-04-11 8:57 ` Ralf Wildenhues
2007-04-11 8:59 ` Paolo Bonzini
2007-04-11 9:23 ` Dave Korn
2007-04-11 9:25 ` Paolo Bonzini
2007-04-11 10:00 ` Dave Korn
2007-04-11 10:19 ` Paolo Bonzini
2007-04-11 21:41 ` Christopher Faylor
2007-04-12 10:42 ` Dave Korn
2007-04-11 2:38 ` Charles Wilson
2007-04-12 6:36 ` Charles Wilson
2007-04-12 7:03 ` Paolo Bonzini
2007-04-12 15:13 ` Steve Ellcey
2007-04-12 18:02 ` Charles Wilson
2007-04-13 7:18 ` Paolo Bonzini
2007-04-13 17:27 ` Steve Ellcey
2007-04-13 18:05 ` Daniel Jacobowitz
2007-04-13 18:18 ` Paolo Bonzini
2007-04-13 18:27 ` Steve Ellcey
2007-04-13 18:38 ` Paolo Bonzini
2007-04-13 18:44 ` Steve Ellcey
2007-04-13 20:19 ` Charles Wilson
2007-04-13 18:24 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=461C8FE6.9010800@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=dave.korn@artimi.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=libtool@cwilson.fastmail.fm \
--cc=newlib@sourceware.org \
--cc=schwab@suse.de \
--cc=sje@cup.hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox