This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: objc failures on branch
- To: Andreas Jaeger <aj at suse dot de>
- Subject: Re: objc failures on branch
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 02 Mar 2001 05:27:10 -0300
- Cc: Nicola Pero <n dot pero at mi dot flashnet dot it>, Zack Weinberg <zackw at stanford dot edu>, gcc-bugs at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <Pine.LNX.3.96.1010228144126.559B-100000@leonardo><hog0gzm36k.fsf@gee.suse.de><oru25c627j.fsf@guarana.lsd.ic.unicamp.br><u8hf1c4mxz.fsf@gromit.rhein-neckar.de>
On Mar 2, 2001, Andreas Jaeger <aj@suse.de> wrote:
> Alexandre Oliva <aoliva@redhat.com> writes:
>> On Feb 28, 2001, Andreas Jaeger <aj@suse.de> wrote:
>>
>> > I'm using a chroot that doesn't contain libgcc_s.so.0:
>>
>> > /usr/bin/ld: warning: libgcc_s.so.0, needed by /usr/src/packages/BUILD/gcc/obj/i486-suse-linux/libobjc/.libs/libobjc.so, not found (try using -rpath or -rpath-link)
>>
>> Then how come libobjc.so ended up depending on it?
> Because it was build correctly:
Err... You had said you didn't have libgcc_s.so.0 in the chrooted
environment. Or I misunderstood.
Anyway, we do have a problem, indeed. libstdc++-v3 has worked around
this by adding the appropriate -rpath flag when building test programs:
2001-02-22 Benjamin Kosnik <bkoz@redhat.com>
* tests_flags.in (CXXFLAGS): Add -rpath to gcc build dir.
However, this assumes libtool is used to link the test programs
(because -rpath isn't portable). What I don't understand is how come
this works for check-g++, given that it doesn't use libtool for
linking, AFAIK. Maybe it's just LD_LIBRARY_PATH? Or is there any
hack in some of the g++-related .exp files that I can't seem to find
right now?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me