From: "Andrea 'fwyzard' Bocci" <fwyzard@inwind.it>
To: Nicola Pero <nicola@brainstorm.co.uk>
Cc: Matthias Klose <doko@cs.tu-berlin.de>, gcc@gcc.gnu.org
Subject: Re: [3.2/3.3/HEAD] shared libobjc not built
Date: Thu, 02 Jan 2003 16:06:00 -0000 [thread overview]
Message-ID: <5.2.0.9.2.20030102165747.00b27e20@popmail.inwind.it> (raw)
In-Reply-To: <Pine.LNX.4.21.0301021543470.3304-100000@nicola.brainstorm. co.uk>
At 15.48 02/01/2003 +0000, Nicola Pero wrote:
> > So, yes, I think it's intended, but I don't know why.
>
>I don't know either ... I don't remember - maybe a historical leftover ?
>
>I think if shared libraries are supported, libobjc should be built as
>shared. It should definitely be built as shared, why building it
>statically ? A static libobjc is usually more of a problem than a shared
>one!
I don't actually use, ObjC, so I don't really know about it But I always
build with --enable-shared, just to be sure :-)
Maybe some Knowledgeable Person here can aswer that...
fwyzard
next prev parent reply other threads:[~2003-01-02 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 15:52 Matthias Klose
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 [this message]
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=5.2.0.9.2.20030102165747.00b27e20@popmail.inwind.it \
--to=fwyzard@inwind.it \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=nicola@brainstorm.co.uk \
/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).