Re: Linking some libraries as static and others as shared

On Tue, Sep 22, 2009 at 9:07 PM, Ralf Wildenhues wrote: > This is a TODO feature: > > > Cheers, > Ralf > Cool. Until then I just wanted to say there's was one omission in this work-around. You must make sure to run AC_LIBTO

Re: Libtool attempts to link 64-bit lib on a -m32 compile (using Pathscale C++)

I'm running into a similar problem, but the -L/usr/lib workaround doesn't help in this case. Same pathCC, but on SuSE 10 (not SuSE 9). The error is basically this: $ make ... libtool: link: pathCC ... -lpscrt /usr/lib64/gcc/x86_64-suse-linux/4.1.2/libstdc++.so -m32 ... /usr/lib64/gcc/x86_

Re: Linking some libraries as static and others as shared

Hello, * dreamcat four wrote on Sat, Sep 19, 2009 at 06:28:23PM CEST: > Is there some safe and architecture - independant way to tell libtool > to link one of the libraries statically, with all others remaining > dynamic? This is a TODO feature:

Re: Linking some libraries as static and others as shared

On Sat, Sep 19, 2009 at 5:28 PM, dreamcat four wrote: > Hi, > Is there some safe and architecture - independant way to tell libtool > to link one of the libraries statically, with all others remaining > dynamic? This is to produce a php-fpm binary file. Well, Here is one solution, which looks in