From: Bryce McKinlay <bryce@albatross.co.nz>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] gcj static linking fix [Re: gcj build on Itanium]
Date: Tue, 27 Feb 2001 09:37:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005216@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
"Boehm, Hans" wrote:
> Problem 5: Static linking tends to result in "eh.o...: undefined reference
> to `fwrite'. This seems to be a library ordering problem, which might also
> affect other platforms.
>
> Workaround: use "-u fwrite" on the command line.
>
> Request: What's a proper fix?
Static libgcc linking seems to require "-lgcc -lc -lgcc" with no other
libraries in between in order to work correctly. The use of libgcj.spec was
adding additional libraries between the first "-lgcc" and the "-lc". This patch
fixes it. I'm checking it in to head + branch.
regards
[ bryce ]
[-- Attachment #2: libgcj.spec.patch --]
[-- Type: text/plain, Size: 710 bytes --]
2001-02-27 Bryce McKinlay <bryce@albatross.co.nz>
* libgcj.spec.in: Insert %(libgcc) before %(liborig) to fix static
linking.
Index: libgcj.spec.in
===================================================================
RCS file: /cvs/gcc/egcs/libjava/libgcj.spec.in,v
retrieving revision 1.13
diff -u -r1.13 libgcj.spec.in
--- libgcj.spec.in 2001/02/05 05:46:16 1.13
+++ libgcj.spec.in 2001/02/27 09:27:45
@@ -4,7 +4,7 @@
# to link with libgcj.
#
%rename lib liborig
-*lib: -lgcj -lm @GCSPEC@ @THREADSPEC@ @ZLIBSPEC@ @SYSTEMSPEC@ %(liborig)
+*lib: -lgcj -lm @GCSPEC@ @THREADSPEC@ @ZLIBSPEC@ @SYSTEMSPEC@ %(libgcc) %(liborig)
*jc1: @DIVIDESPEC@ @EXCEPTIONSPEC@ @JC1GCSPEC@ -fasynchronous-exceptions
reply other threads:[~2001-02-27 9:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590693005216@msgid-missing \
--to=bryce@albatross.co.nz \
--cc=linux-ia64@vger.kernel.org \
/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