This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: sh-unknown-linux-gnu (Support of specific targets (sh3, sh4, sh3eb, and sh4eb))
- To: "M. R. Brown" <mrbrown at 0xd6 dot org>
- Subject: Re: sh-unknown-linux-gnu (Support of specific targets (sh3, sh4, sh3eb, and sh4eb))
- From: NIIBE Yutaka <gniibe at m17n dot org>
- Date: Tue, 2 Oct 2001 16:30:51 +0900 (JST)
- Cc: gcc-patches at gcc dot gnu dot org, kaz Kojima <kkojima at rr dot iij4u dot or dot jp>, rodrigc at gcc dot gnu dot org, aoliva at redhat dot com, amylaar at redhat dot com
- References: <200110020413.f924D4c09833@mule.m17n.org><20011002021901.A1419@0xd6.org>
M. R. Brown wrote:
> What's with the custom -rpath-link options? These look very specific to a
> customized setup, why are the being included in the generic (unknown)
> linux.h ?
>
> Doesn't GCC and binutils already know where to look for multilibbed
> libraries?
Good point. No, it doesn't know for shared library.
I think that we should not have needed such things. However, current
binutils (at least) doesn't look multilib for shared libraries.
Supporse ldscripts of binutils are $PATH_TO_LDSCRIPTS, then, it
searches $PATH_TO_LDSCRIPTS/../ (upper directory of ldscript). In
case of $PATH_TO_LDSCRIPTS == /usr/sh-linux/lib/ldscripts,
it (only) searches /usr/sh-linux/lib for shared library.
And for me, there's no way to avoid specific path (/usr/sh-linux) in
the spec file. Do you have any idea?
--