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 03:28:00 -0000 [thread overview]
Message-ID: <A1020E28-1F94-11D7-99C2-0003933F3BC2@omnigroup.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0301030331170.8242-100000@nicola.brainstorm.co.uk>
On Thursday, January 2, 2003, at 07:54 PM, Nicola Pero wrote:
> If you can get some time to get it working on MinGW, that would be
> great
> :-)
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...)
This patch is against the gcc-3.2.1-20021201-3 MinGW tarball, but I
wouldn't be surprised if it worked on the head too :)
--- ./ltcf-c.sh Fri Aug 31 17:47:19 2001
+++ ../../gcc-3.2.1-20021201-3/ltcf-c.sh Fri Jan 3 19:18:51 2003
@@ -102,7 +102,7 @@
# hardcode_libdir_flag_spec is actually meaningless, as there is
# no search path for DLLs.
hardcode_libdir_flag_spec='-L$libdir'
- allow_undefined_flag=unsupported
+ allow_undefined_flag=
always_export_symbols=yes
extract_expsyms_cmds='test -f $output_objdir/impgen.c || \
@@ -160,9 +160,9 @@
_lt_hint=1;
cat $export_symbols | while read symbol; do
set dummy \$symbol;
- case \[$]# in
- 2) echo " \[$]2 @ \$_lt_hint ; " >>
$output_objdir/$soname-def;;
- *) echo " \[$]2 @ \$_lt_hint \[$]3 ; " >>
$output_objdir/$soname-def;;
+ case \$# in
+ 2) echo " \$2 @ \$_lt_hint ; " >>
$output_objdir/$soname-def;;
+ *) echo " \$2 @ \$_lt_hint \$3 ; " >>
$output_objdir/$soname-def;;
esac;
_lt_hint=`expr 1 + \$_lt_hint`;
done;
This turns off the setting of 'allow_undefined_flag=unsupported'
since the ObjC DLL doesn't *have* any undefined symbols, so there is no
need to allow them! Also, this changes the shell syntax to not bork
the defs file -- It could well be that /bin/sh is busted on Mac OS X
(from whence I'm cross compiling), but it is now bash:
% /bin/sh --version
GNU bash, version 2.05a.0(1)-release (powerpc-apple-darwin6.0)
Copyright 2001 Free Software Foundation, Inc.
... so I'd expect it to be reasonably close to what other folks have.
I'll let you all know if I can get the DLL actually working in a bit.
:)
-tim
next prev parent reply other threads:[~2003-01-04 3:28 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 [this message]
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=A1020E28-1F94-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).