From: Steve Ellcey <sje@cup.hp.com>
To: pinskia@gmail.com
Cc: binutils@sourceware.org, gcc-patches@gcc.gnu.org,
gdb-patches@gcc.gnu.org, newlib@sourceware.org,
Ralf.Wildenhues@gmx.de, aoliva@redhat.com, bonzini@gnu.org,
fxcoudert@gmail.com, libtool@cwilson.fastmail.fm,
schwab@suse.de
Subject: Re: Final(?) patch to update libtool in GCC and src trees
Date: Tue, 10 Apr 2007 20:04:00 -0000 [thread overview]
Message-ID: <200704102003.NAA21144@hpsje.cup.hp.com> (raw)
In-Reply-To: <de8d50360704101142t570844ddm32f1a814208f064b@mail.gmail.com>
> Hmm, this usually means something is not being exported correctly from
> libobjc.so, can you do a nm on generated libobjc.so?
>
> Thanks,
> Andrew Pinski
% nm obj_gcc/ia64-debian-linux-gnu/libobjc/.libs/libobjca.so | grep person
0000000000027d10 T __gnu_objc_personality_v0
It looks like it is geing exported correctly.
It may be an issue with how the objc tests (compile tests, not library tests)
are being called during testing. Here is an example failure from
gcc/testsuite/objc.dg:
set_ld_library_path_env_vars: ld_library_path=.::/proj/opensrc/nightly/build-ia64-debian-linux-gnu-trunk/obj_gcc/gcc:/proj/opensrc/nightly/build-ia64-debian-linux-gnu-trunk/obj_gcc/gcc:/proj/opensrc/nightly/build-ia64-debian-linux-gnu-trunk/obj_gcc/gcc:/proj/opensrc/nightly/build-ia64-debian-linux-gnu-trunk/obj_gcc/gcc
Executing on host: /proj/opensrc/nightly/build-ia64-debian-linux-gnu-trunk/obj_gcc/gcc/xgcc -B/proj/opensrc/nightly/build-ia64-debian-linux-gnu-trunk/obj_gcc/gcc/ /proj/opensrc/nightly/src/trunk/gcc/testsuite/objc.dg/bitfield-1.m -lobjc -lm -o ./bitfield-1.exe (timeout = 300)
/proj/opensrc/be/ia64-debian-linux-gnu/lib/gcc/ia64-debian-linux-gnu/4.1.1/../../../../ia64-debian-linux-gnu/bin/ld: cannot find -lobjc
collect2: ld returned 1 exit status
compiler exited with status 1
output is:
/proj/opensrc/be/ia64-debian-linux-gnu/lib/gcc/ia64-debian-linux-gnu/4.1.1/../../../../ia64-debian-linux-gnu/bin/ld: cannot find -lobjc
collect2: ld returned 1 exit status
FAIL: objc.dg/bitfield-1.m (test for excess errors)
next prev parent reply other threads:[~2007-04-10 20:04 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 [this message]
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
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=200704102003.NAA21144@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=libtool@cwilson.fastmail.fm \
--cc=newlib@sourceware.org \
--cc=pinskia@gmail.com \
--cc=schwab@suse.de \
/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