Re: Use of compiler_lib_search_path when cross-compiling

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 > > > libt

Re: Use of compiler_lib_search_path when cross-compiling

On Tue, Sep 06, 2005 at 11:50:22PM -0500, Albert Chin wrote: > If CC=[cross-compile gcc], then shouldn't "$CC -print-search-dirs" set > $compiler_lib_search_path correctly? Yes, but I need both. I am building some packages (e.g. bison, coreutils) and some packages for the target.

Re: Use of compiler_lib_search_path when cross-compiling

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 > > bu

Re: Use of compiler_lib_search_path when cross-compiling

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

Use of compiler_lib_search_path when cross-compiling

I'm still tracking a problem where libtool adds native libraries to the link when cross-compiling. I've upgraded to 1.5.20, just to make sure that this hasn't yet been fixed. Here's what I've found. There appear to be two factors at play. First is the postdeps: # Dependencies to place after

Re: libtool stdout output format

Hi Ralf and others, Ralf Wildenhues wrote: As of now, the output format -- "whatever libtool prints on stdout" -- is different between the 1.5 releases and CVS HEAD. The latter prepends a string like libtool: $mode: where mode is either `compile', `link', or similar. This output has never

libtool stdout output format

As of now, the output format -- "whatever libtool prints on stdout" -- is different between the 1.5 releases and CVS HEAD. The latter prepends a string like libtool: $mode: where mode is either `compile', `link', or similar. This output has never been formally specified, neither is it complete

Re: Wondering if libtool can be adapted, ported, or used to solve my problem

Hi Travis, * Travis Spencer wrote on Sat, Sep 03, 2005 at 12:02:15AM CEST: > > I am working on a research project at Portland State University that > involves writing an application that will build its user's source code > and gather a lot of information about the build process and host > environ