From: "Timothy J. Wood" <tjw@omnigroup.com>
To: Nicola Pero <nicola@brainstorm.co.uk>
Cc: 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 05:58:00 -0000 [thread overview]
Message-ID: <76653E93-1FA9-11D7-99C2-0003933F3BC2@omnigroup.com> (raw)
In-Reply-To: <A1020E28-1F94-11D7-99C2-0003933F3BC2@omnigroup.com>
On Friday, January 3, 2003, at 07:28 PM, Timothy J. Wood wrote:
> OK, I have it generating a dll file now. I still need to test if
> ObjC *works* with the DLL, but I thought I'd run this diff out to see
> if anyone spots any problems this might cause (I can't imagine what,
> but...)
The DLL seems to work.
The only issues are:
- The install doesn't create a symlink from from libobjc.dll to
libobjc-1.dll (my cross host is Unix, so a symlink should work fine)
- '--disable-static' doesn't prevent the libobjc.a from getting built
Still, the patch seems like a big improvement since I can actually
*use* a DLL now. I can manually fix the items above trivially, so if
someone could commit the ltcf-c.sh patch in MinGW and on the head of
whatever GCC branches are appropriate, that would be great (or I can
send the patch again to gcc-patches, if that is required).
-tim
next prev parent reply other threads:[~2003-01-04 5:58 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 [this message]
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=76653E93-1FA9-11D7-99C2-0003933F3BC2@omnigroup.com \
--to=tjw@omnigroup.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 \
/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).