This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: sh-unknown-linux-gnu (Support of specific targets (sh3, sh4, sh3eb, and sh4eb))


* NIIBE Yutaka <gniibe@m17n.org> on Tue, Oct 02, 2001:

> 
> + /* XXX: It's wrong if prefix != /usr */
>   #undef LINK_SPEC
>   #define LINK_SPEC \
> !   "%{!mb:-m shlelf_linux -EL} %{mb:-m shelf_linux -EB} %{mrelax:-relax} \
>      %{shared:-shared} \
>      %{!static: \
>        %{rdynamic:-export-dynamic} \
>        %{!dynamic-linker:-dynamic-linker /lib/ld-linux.so.2} \
> !      %{!mb:%{!m4:-rpath-link /usr/sh-linux/lib }} \
> !      %{!mb:%{m4:-rpath-link /usr/sh-linux/lib/m4 }} \
> !      %{mb:%{!m4:-rpath-link /usr/sh-linux/lib/mb }} \
> !      %{mb:%{m4:-rpath-link /usr/sh-linux/lib/mb/m4 }}} \
>      %{static:-static}"
>   

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?

M. R.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]