From: Matthias Klose <doko@cs.tu-berlin.de>
To: gcc@gcc.gnu.org
Subject: [3.2/3.3/HEAD] shared libobjc not built
Date: Wed, 01 Jan 2003 15:52:00 -0000 [thread overview]
Message-ID: <15891.3498.853850.742335@gargle.gargle.HOWL> (raw)
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.
[...]
checking whether the linker (ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking command to parse nm output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
creating libtool
updating cache ../config.cache
loading cache ../config.cache
[...]
next reply other threads:[~2003-01-01 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 15:52 Matthias Klose [this message]
2003-01-02 15:31 ` Andrea 'fwyzard' Bocci
2003-01-02 15:48 ` Nicola Pero
[not found] ` <Pine.LNX.4.21.0301021543470.3304-100000@nicola.brainstorm. co.uk>
2003-01-02 16:06 ` Andrea 'fwyzard' Bocci
2003-01-02 16:32 ` Nicola Pero
2003-01-02 20:54 ` Timothy J. Wood
2003-01-03 0:01 ` Nicola Pero
2003-01-03 0:46 ` Timothy J. Wood
2003-01-03 3:55 ` Nicola Pero
2003-01-04 3:28 ` Timothy J. Wood
2003-01-04 5:58 ` Timothy J. Wood
2003-01-04 14:23 ` [MinGW-patches] " Earnie Boyd
2003-01-04 18:10 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15891.3498.853850.742335@gargle.gargle.HOWL \
--to=doko@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).