[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Use of compiler_lib_search_path when cross-compiling
From: |
Albert Chin |
Subject: |
Re: Use of compiler_lib_search_path when cross-compiling |
Date: |
Tue, 6 Sep 2005 23:50:22 -0500 |
User-agent: |
Mutt/1.5.6i |
On Tue, Sep 06, 2005 at 07:06:13PM -0700, Marc Singer wrote:
> On Tue, Sep 06, 2005 at 08:57:24PM -0500, Albert Chin wrote:
> > On Tue, Sep 06, 2005 at 04:22:03PM -0700, Marc Singer wrote:
> > > [ snip snip ]
> > >
> > > So, the question is this. Do I need to build a special version of
> > > libtool for cross compiling which is separate from the version used to
> > > build native packages?
> >
> > Yes. However, libtool is usually part of the native package build
> > process so it gets customized to whatever flags used during the build.
> > It's generally a bad idea to use the installed libtool unless you're
> > using the same flags used to build the installed libtool.
>
> No. I'm not using the installed libtool. I'm building it as part of
> the cross-development environment. Now, I know that I have to build
> two version: one for native packages and one for cross-compiled
> packages.
If CC=[cross-compile gcc], then shouldn't "$CC -print-search-dirs" set
$compiler_lib_search_path correctly?
--
albert chin (address@hidden)