How does the configure process decide to create shared libraries?

David Daney ddaney@avtrex.com
Tue Apr 6 01:17:00 GMT 2004


I am trying to build gcc 3.4.0 from today's CVS (but with some of my own 
modifications), configured as a cross compiler.

Host: i686-pc-linux
Target: mipsel-linux-uclibc

../gcccvsw/gcc/configure  --host=i686-pc-linux-gnu 
--target=mipsel-linux-uclibc --enable-languages=c,c++,java 
--with-arch=mips32 --with-float=soft --with-sysroot=/home/mipsel-uClibc 
--prefix=/home/mipsel-uClibc --enable-shared

I have hacked up some things to get the mipsel-linux-uclibc to mostly work.

The problem I am having that the build does not create shared versions 
of libgcj and libstdc++.  Only archive libraries of these are built.  It 
does however create the libgcc_s.so.

The libtools in the configured libjava and libstdc++-v3 directories 
contain the lines:

# Whether or not to build shared libraries.
build_libtool_libs=no
 
Here is my question:  Which part of the configure process controls 
setting build_libtool_libs to yes or no?

How would I go about making it say "yes"?

Thanks in advance,

David Daney.




More information about the Gcc mailing list