This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [3.2/3.3/HEAD] shared libobjc not built
- From: "Andrea 'fwyzard' Bocci" <fwyzard at inwind dot it>
- To: Matthias Klose <doko at cs dot tu-berlin dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 02 Jan 2003 16:30:40 +0100
- Subject: Re: [3.2/3.3/HEAD] shared libobjc not built
At 16.47 01/01/2003 +0100, Matthias Klose wrote:
gcc configured without explicit --enabled-shared builds shared
libraries for libstdc++, libgcj, etc, but not for libobjc (i386-linux)
Is this intended? libobjc's configure sets the default to disabled.
From <http://gcc.gnu.org/install/configure.html>:
--enable-shared[=package[,...]]
Build shared versions of libraries, if shared libraries are supported on
the target platform. Unlike GCC 2.95.x and earlier, shared libraries are
enabled by default on all platforms that support shared libraries, except
for libobjc which is built as a static library only by default.
If a list of packages is given as an argument, build shared libraries only
for the listed packages. For other packages, only static libraries will be
built. Package names currently recognized in the GCC tree are libgcc (also
known as gcc), libstdc++ (not libstdc++-v3), libffi, zlib, boehm-gc and
libjava. Note that libobjc does not recognize itself by any name, so, if
you list package names in --enable-shared, you will only get static
Objective-C libraries. libf2c and libiberty do not support shared
libraries at all.
So, yes, I think it's intended, but I don't know why.
fwyzard