Re: Help: 64 Bit Solaris 10

[Edward Maros]

Bob Friesenhahn wrote:

> 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 dynamicly creating the libtool shell 
> > script as part of the configuration of a package. With GCC being able 
> > to support 32bit and 64bit compilations, it would be nice if libtool 
> > would have the same or similar flexibility. I do recognize that 
> > libtool has the additional complication that it has to make decisions 
> > based on the compiler being used to compile the application.
>
>
> Libtool is most often configured as part of a package and a custom 
> libtool script is "dynamicly created" based on supplied configuration 
> options.  How would you like it to behave differently?

Maybe I have the wrong model. What I have done is to compile libtool for 
Solaris for all the developers to use. It is installed using the same 
prefix as GCC. When I then use it as part of a software package, I 
simply use the AM_PROG_LIBTOOL macro in my configure.in file. When I did 
this, I got rules appropriate for 32-bit compilation even though I 
configured my package to include -m64 in the CFLAGS and CXXFLAGS.

Based on input that I received from this list, I rebuilt my version of 
libtool using the -m64 flag which allowed me to use it for 64 bit 
compiles. It does mean that anyone else wanting to use libtool will have 
to be compiling 64 bit.

Are you suggesting that I include the libtool source distribution with 
my package and configure it as part of my distribution?

> Bob
> ======================================
> Bob Friesenhahn
> address@hidden, 
> http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

Thanks,
Ed

smime.p7s
Description: S/MIME Cryptographic Signature