From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Sat Feb 06 1999 - 21:35:03 EST
On Feb 7, 1999, Godmar Back <gback@cs.utah.edu> wrote:
>>
>> On Feb 6, 1999, Godmar Back <gback@cs.utah.edu> wrote:
>>
>> > When doing "make AM_CFLAGS=-static", I see this:
>> You must `configure --enable-static' in order to be able to create
>> static libraries. This is a known problem in libtool.
> Then why is libtool compiling everything twice?
> I thought it was to build both the pic and nonpic versions?
It isn't (shouldn't) be compiling everything twice unless you
`configure --enable-static --enable-shared'. Currently, configure
implicitly --disable-static unless --with-staticlib and/or
--with-staticvm. If both --with-staticlib and --with-staticvm are
issued, you should get --disable-shared.
> Why does it build both versions if it can't build static libraries
> from the nonpic versions? And why is that a known problem?
It isn't building the nonpic versions, but sometimes it misses this
fact and tries to use them anyway.
> Wasn't the whole point of libtool that I didn't have to say
> --with-staticlib anymore if I wanted to have statically linked libs?
We --disable-static by default so as to avoid double-compilation. If
you want to override this, you must --enable-static manually, until
this libtool bug is fixed.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:59 EDT