This is the mail archive of the gcc@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]
Other format: [Raw text]

Re: [discuss] Re: Absolute paths horror in gcc


>  In message <20020318121210.11519DA2C7@pluto.sonofthor.dk>, Bo Thorsen writes:
>  > The problem is that gcc doesn't have the infrastructure needed to make it 
>  > look in two different places for the crt files.
> It does if you use multi-libs.  I haven't thought a lot about it, but it may
> be a relatively clean way to deal with your problem.

We do use multilibs.  Problem I see is that the gcc.c does search always
at the standrard paths /usr/lib, /lib etc., while we want it to search
on /usr/lib64, /lib64 depending whether -m32 or -m64 or nothing is specified.

I don't see how this can be acoomplished easilly as -m32/-m64 is not understood
by driver IMO. Or am I missing something important?
Perhaps I've missconfigured the multilibs.

Honza
> 
> jeff
> 


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