From: Alexandre Oliva <aoliva@redhat.com>
To: "Timothy J. Wood" <tjw@omnigroup.com>
Cc: Nicola Pero <nicola@brainstorm.co.uk>,
gcc@gcc.gnu.org, Matthias Klose <doko@cs.tu-berlin.de>,
"Andrea 'fwyzard' Bocci" <fwyzard@inwind.it>,
mingw-patches@lists.sourceforge.net
Subject: Re: [3.2/3.3/HEAD] shared libobjc not built
Date: Sat, 04 Jan 2003 18:10:00 -0000 [thread overview]
Message-ID: <orsmw8iyo1.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <A1020E28-1F94-11D7-99C2-0003933F3BC2@omnigroup.com>
On Jan 4, 2003, "Timothy J. Wood" <tjw@omnigroup.com> wrote:
> This turns off the setting of 'allow_undefined_flag=unsupported'
> since the ObjC DLL doesn't *have* any undefined symbols,
Then it can be linked with libtool's -no-undefined flag, and then
libtool will create a dynamic library. Changing allow_undefined_flag
will just cause libtool to attempt to build libraries that do have
undefined symbols as shared, which fails.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
prev parent reply other threads:[~2003-01-04 18:00 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
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 [this message]
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=orsmw8iyo1.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=doko@cs.tu-berlin.de \
--cc=fwyzard@inwind.it \
--cc=gcc@gcc.gnu.org \
--cc=mingw-patches@lists.sourceforge.net \
--cc=nicola@brainstorm.co.uk \
--cc=tjw@omnigroup.com \
/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).