public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "andreast at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/17222] libjava fails to build due to command line length during link
Date: Mon, 30 Aug 2004 19:15:00 -0000 [thread overview]
Message-ID: <20040830191554.2569.qmail@sourceware.org> (raw)
In-Reply-To: <20040828135005.17222.kcook@gcc.gnu.org>
------- Additional Comments From andreast at gcc dot gnu dot org 2004-08-30 19:15 -------
oh, now I seem to remember why shared libraries are not supported under darwin <
7.0. Afair it was due to the missing MD_FALLBACK_FRAME_STATE_FOR macro at the
time when I introduced the changes for shared libraries on darwin.
Now this macro is in and it should also support darwin < 7.0.
You may try to modify ltcf-c.sh, ltcf-cxx.sh, ltcf-gcj.sh and ltconfig in the
toplevel gcc dir. See where it says:
case $host_os in
darwin[1-6]*)
can_build_shared=no
;;
darwin7*)
can_build_shared=yes
;;
esac
To say yes for darwin6.x too. It may help. I don't know since I no longer have a
6.x machine around. Just an idea.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17222
next prev parent reply other threads:[~2004-08-30 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 13:50 [Bug libgcj/17222] New: " kcook at gcc dot gnu dot org
2004-08-28 13:52 ` [Bug libgcj/17222] " kcook at gcc dot gnu dot org
2004-08-28 17:14 ` pinskia at gcc dot gnu dot org
2004-08-30 18:20 ` andreast at gcc dot gnu dot org
2004-08-30 18:37 ` mckinlay at redhat dot com
2004-08-30 19:15 ` andreast at gcc dot gnu dot org [this message]
2004-09-23 11:46 ` kcook at gcc dot gnu dot org
2004-09-23 12:14 ` aph at gcc dot gnu dot org
2004-09-27 22:31 ` tromey at gcc dot gnu dot org
2004-09-28 17:37 ` kcook at gcc dot gnu dot org
2004-09-28 20:37 ` cvs-commit at gcc dot gnu dot org
2004-09-28 20:39 ` tromey at gcc dot gnu dot org
2004-09-28 21:22 ` lars dot sonchocky-helldorf at hamburg dot de
2004-10-09 16:08 ` lars dot sonchocky-helldorf at hamburg dot de
2005-03-02 18:25 ` kcook at gcc dot gnu dot org
2005-03-02 18:25 ` kcook at gcc dot gnu dot org
2005-03-02 21:41 ` pinskia at gcc dot gnu dot org
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=20040830191554.2569.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).