Re: Reducing dependency_libs to what was on the command line.

On Tue, Dec 06, 2005 at 06:46:16PM +0100, Ralf Wildenhues wrote: > * Jacob Meuser wrote on Tue, Dec 06, 2005 at 09:43:05AM CET: > > On Tue, Dec 06, 2005 at 08:25:15AM +0100, Ralf Wildenhues wrote: > > > > > - or, and that is more important, where a lot of the installed > > > libraries simply wer

Re: Help: 64 Bit Solaris 10

On Tue, 6 Dec 2005, Edward Maros wrote: Thanks to everyone's suggestions. It has been very insightful on how libtool works. I am now able to compile my applications for 64bit Solaris. With the insight that I received from this exercise, I was wondering if any thought had been given to dynami

Re: Help: 64 Bit Solaris 10

Ralf Wildenhues wrote: * Tim Rice wrote on Tue, Dec 06, 2005 at 02:25:32AM CET: On Mon, 5 Dec 2005, Edward Maros wrote: This may be a frequent question, but I have not been able to find a solution yet. I am trying to port out application to 64bit using a sparc4u running Solaris 10. Th

Re: Libltdl configure options

Hi Thomas, * Thomas Degris wrote on Tue, Dec 06, 2005 at 09:54:06AM CET: > > I am using libltdl in my project called Satom > (http://savannah.nongnu.org/projects/satom/). Satom uses automake to > handle the compilation process. However, I have some troubles > configuring (with the configure sc

Re: Reducing dependency_libs to what was on the command line.

On Tue, Dec 06, 2005 at 08:25:15AM +0100, Ralf Wildenhues wrote: > > Well. Given above thoughts, I would think that your change makes sense > in the link_all_deplibs=no setting, given that the package author knows > about this. > > Erm. Except: what about static linking in that case? > I think

Re: Reducing dependency_libs to what was on the command line.

* Jacob Meuser wrote on Tue, Dec 06, 2005 at 09:43:05AM CET: > On Tue, Dec 06, 2005 at 08:25:15AM +0100, Ralf Wildenhues wrote: > > > - or, and that is more important, where a lot of the installed > > libraries simply were never created with libtool, e.g., because > > they stem from a propriet

Re: Use of printf in libtool.m4

* Peter O'Gorman wrote on Tue, Dec 06, 2005 at 02:37:20PM CET: > > Just looking to put in an honest check for -single_module support into > libtool.m4 and I see this in _LT_COMPILER_OPTION: > printf "$lt_simple_compile_test_code" > conftest.$ac_ext > > with similar usage elsewhere. > > Why do w

Re: Implementing LIBTOOL on OpenVMS

Ralf Wildenhues wrote: Hi John, [ not responding to everyting ] * John E. Malmberg wrote on Mon, Dec 05, 2005 at 09:14:05PM CET: So it would be better if the library authors provided a list. Hmm. Maybe you can convince a few. If the list can be kept platform- independent, maybe a few more

Re: PIC flags in mode=link

Hi Christopher, * Christopher Hulbert wrote on Tue, Dec 06, 2005 at 10:27:39AM CET: > Is there a reason that libtool doesn't pass PIC flags during the link > of shared libraries? And if it's passed as -fpic to the libtool > command, libtool strips it out. The way to get it through is use > -Wc,-

Use of printf in libtool.m4

Hi, Just looking to put in an honest check for -single_module support into libtool.m4 and I see this in _LT_COMPILER_OPTION: printf "$lt_simple_compile_test_code" > conftest.$ac_ext with similar usage elsewhere. Why do we go to so much effort to find a working echo if printf works everywhere

PIC flags in mode=link

Is there a reason that libtool doesn't pass PIC flags during the link of shared libraries? And if it's passed as -fpic to the libtool command, libtool strips it out. The way to get it through is use -Wc,-fpic in my LDFLAGS, but then pgcc complains that -f is invalid without -shared when building

Libltdl configure options

Hello, I am using libltdl in my project called Satom (http://savannah.nongnu.org/projects/satom/). Satom uses automake to handle the compilation process. However, I have some troubles configuring (with the configure script) Satom with libltdl on mingw. When I pass options to configure to set

Re: Reducing dependency_libs to what was on the command line.

On Tue, Dec 06, 2005 at 08:25:15AM +0100, Ralf Wildenhues wrote: > - or, and that is more important, where a lot of the installed > libraries simply were never created with libtool, e.g., because > they stem from a proprietary OS. or from BSD ... -- <[EMAIL PROTECTED]> ___

Re: Implementing LIBTOOL on OpenVMS

Hi John, [ not responding to everyting ] * John E. Malmberg wrote on Mon, Dec 05, 2005 at 09:14:05PM CET: > > No problem, I am fighting with pkg-config right now. I'm sorry. > Ralf Wildenhues wrote: > > I had to read a bit about OpenVMS first. > > I assume that you found the documentation li