From: Steve Ellcey <sje@cup.hp.com>
To: libtool@cwilson.fastmail.fm, gcc-patches@gcc.gnu.org,
libstdc++@gcc.gnu.org
Subject: Re: Patch to update libtool in GCC and binutils trees
Date: Fri, 30 Mar 2007 18:29:00 -0000 [thread overview]
Message-ID: <200703301747.KAA23706@hpsje.cup.hp.com> (raw)
In-Reply-To: <460C8A2B.5010108@cwilson.fastmail.fm>
Charles Wilson wrote:
> LIBSUPCXX_PICFLAGS=
> test "$enable_shared" = yes && LIBSUPCXX_PICFLAGS=-prefer-pic
Thanks, testing $enable_shared fixes the build problem.
I still have a problem when testing libstdc++. On IA64 HP-UX, when
testing in 64 bit mode, I look at
obj_gcc/ia64-hp-hpux11.23/hpux64/libstdc++-v3/testsuite/Makefile
and I see:
CXX = /proj/opensrc/nightly/build-ia64-hp-hpux11.23-trunk/obj_gcc/./gcc/xgcc -shared-libgcc -B/proj/opensrc/nightly/build-ia64-hp-hpux11.23-trunk/obj_gcc/./gcc -nostdinc++ -L/proj/opensrc/nightly/build-ia64-hp-hpux11.23-trunk/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/src -L/proj/opensrc/nightly/build-ia64-hp-hpux11.23-trunk/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/src/.libs -B/proj/opensrc/nightly/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/bin/ -B/proj/opensrc/nightly/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/lib/ -isystem /proj/opensrc/nightly/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/include -isystem /proj/opensrc/nightly/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/sys-include
The problem is:
-L/proj/opensrc/nightly/build-ia64-hp-hpux11.23-trunk/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/src
-L/proj/opensrc/nightly/build-ia64-hp-hpux11.23-trunk/obj_gcc/ia64-hp-hpux11.23/libstdc++-v3/src/.libs
These don't have the 'hpux64' multilib directory inserted between
ia64-hp-hpux11.23 and libstdc++-v3. When I do a build/test with the old
libtool the hpux64 directory is there.
Any idea on where this is going wrong?
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2007-03-30 17:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 4:16 Charles Wilson
2007-03-30 18:29 ` Steve Ellcey [this message]
2007-04-02 11:22 ` Ralf Wildenhues
2007-04-02 21:05 ` Steve Ellcey
2007-04-05 7:06 ` Alexandre Oliva
2007-04-02 11:19 ` Ralf Wildenhues
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 22:21 Steve Ellcey
2007-04-05 22:54 ` Alexandre Oliva
2007-04-06 16:24 ` Steve Ellcey
2007-04-06 16:59 ` Benjamin Kosnik
[not found] <200703281744.l2SHin837088@makai.watson.ibm.com>
[not found] ` <200703282231.PAA13113@hpsje.cup.hp.com>
2007-03-30 10:24 ` François-Xavier Coudert
2007-03-30 11:56 ` François-Xavier Coudert
2007-04-02 11:21 ` Ralf Wildenhues
2007-04-02 11:25 ` Paolo Bonzini
2007-03-23 17:12 Steve Ellcey
2007-03-26 16:58 ` Steve Ellcey
2007-03-26 18:01 ` Paolo Bonzini
2007-03-29 16:58 ` Steve Ellcey
2007-03-29 17:05 ` Andreas Schwab
2007-03-29 19:25 ` Steve Ellcey
2007-03-29 23:01 ` Steve Ellcey
2007-04-05 6:58 ` Alexandre Oliva
2007-03-30 7:24 ` Ben Elliston
2007-03-23 9:45 Paolo Bonzini
[not found] ` <200703231550.IAA20980@hpsje.cup.hp.com>
2007-03-23 16:37 ` François-Xavier Coudert
2007-03-23 0:10 FX Coudert
2007-03-22 21:48 Steve Ellcey
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=200703301747.KAA23706@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=libtool@cwilson.fastmail.fm \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).