From: "Timothy J. Wood" <tjw@omnigroup.com>
To: Nicola Pero <nicola@brainstorm.co.uk>
Cc: "Andrea 'fwyzard' Bocci" <fwyzard@inwind.it>,
Matthias Klose <doko@cs.tu-berlin.de>,
gcc@gcc.gnu.org
Subject: Re: [3.2/3.3/HEAD] shared libobjc not built
Date: Fri, 03 Jan 2003 00:46:00 -0000 [thread overview]
Message-ID: <A49A398C-1EB4-11D7-B25D-0003938E4E3C@omnigroup.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0301022351320.7756-100000@nicola.brainstorm.co.uk>
On Thursday, January 2, 2003, at 04:00 PM, Nicola Pero wrote:
> Thanks - 'problems building shared objc in MinGW' - do you mean it
> doesn't
> compile, or just that once you've compiled it, it's quite useless ?
My personal experience was that the MinGW distribution just wouldn't
build a DLL for ObjC. I don't recall whether it was an error, or
whether they inherited the configury from GCC that disabled shared
libraries (for some other reason). The responses I got on the MinGW
list (around 1/6/2002) indicated that I should just use the GNUstep
version.
The only indication I see of *why* is that the GNUstep version had
different configury bits and a .def file to export the right symbols.
I'm assuming there was some real problem, but it's been so long ago
that I may be misremembering and it might be that MinGW's problem is an
effect of GCC's problem, not the other way around.
[...]
> building libobjc as static on MinGW is not really a solution either,
> as it
> seems a libobjc.a on MinGW is not really a usable thing :-) [I think
> the
> problem starts when people build all other libraries as DLLs, and
> mixing
> DLLs and static libs doesn't seem a good thing ... well I don't really
> know, but that's what I heard].
Building libobjc static under MinGW doesn't work well if your other
libraries are DLLs _and_ if you want to get good warnings about
undefined symbols in your DLLs. You can link the static library into
main application and then not link it into your DLLs (linking in both
causes madness since you get multiple copies of the ObjC runtime data).
I don't recall why didn't go this direction unless it was that I
somehow couldn't get DLLs to link with the undefined ObjC symbols...
> I suppose what we'd really want then is to fix building the libobjc
> shipped with GCC as a DLL on MinGW. :-)
>
> I don't have the time to work on this.
Yes, I'd definitely like this -- assuming ObjC as a shared library
works in GCC now, I can maybe scrounge up some time to get it working
on MinGW.
I assume all I'd need to do would be to remove 'AC_DISABLE_SHARED'
and then reconfigure?
-tim
next prev parent reply other threads:[~2003-01-03 0:46 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 [this message]
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=A49A398C-1EB4-11D7-B25D-0003938E4E3C@omnigroup.com \
--to=tjw@omnigroup.com \
--cc=doko@cs.tu-berlin.de \
--cc=fwyzard@inwind.it \
--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).