From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gcc-patches@gcc.gnu.org, binutils@gcc.gnu.org,
gdb-patches@gcc.gnu.org, newlib@sourceware.org
Subject: Re: Patch to update libtool in GCC and binutils trees
Date: Mon, 26 Mar 2007 17:31:00 -0000 [thread overview]
Message-ID: <46080332.4020403@lu.unisi.ch> (raw)
In-Reply-To: <200703261632.JAA15792@hpsje.cup.hp.com>
Steve Ellcey wrote:
> I tested the new libtool on HP-UX and Linux over the weekend. The
> builds all worked fine but I got many C++ failures during testing on
> IA64 HP-UX, PA HP-UX (32 bits), and x86_64 Linux. All the failures
> seemed to involve trouble finding the libstdc++ library when linking
> test programs. On IA64 HP-UX, testing worked in default 32 bit mode but
> failed in 64 bit mode because we have a -L that finds the 32 bit
> libstdc++ library before one that finds the 64 bit version. On PA and
> x86_64, we just don't seem to find libstdc++ at all.
>
> I'll see if I can figure out what is going on.
Thanks. By the way, next time it's best if you don't post the
new libtool files as a patch, but just attach them or a .tar.gz
of them. Just post the configure.ac/Makefile.am changes as diffs.
Sorry for not asking for this the previous time.
Paolo
next prev parent reply other threads:[~2007-03-26 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 16:22 Steve Ellcey
2007-03-26 16:32 ` Steve Ellcey
2007-03-26 17:31 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-23 7:29 Paolo Bonzini
[not found] ` <200703231550.IAA20980@hpsje.cup.hp.com>
2007-03-23 16:12 ` François-Xavier Coudert
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=46080332.4020403@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=binutils@gcc.gnu.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=newlib@sourceware.org \
--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