From: Calvin Austin <caustin@spikesource.com>
To: "Petteri Räty" <betelgeuse@gentoo.org>
Cc: Gentoo Java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] FYI in case you wondering why 1.6 needs libstdc++.so.5
Date: Tue, 11 Dec 2007 09:43:39 +0530 [thread overview]
Message-ID: <1197346419.6612.16.camel@localhost.localdomain> (raw)
In-Reply-To: <475DA72B.4060600@gentoo.org>
Static linking is normally considered bad practice but in reality for
linux it was the only way we could get a JDK to run on a reasonable
amount of platforms.
Sun doesn't have the bandwidth to test all distributions however it is
now confusing that the earlier release java 5.0 supports RHEL5 whereas
the newer release doesn't. Hopefully someone will back port the fix from
java 7.0 to java 6.0
regards
calvin
On Mon, 2007-12-10 at 22:52 +0200, Petteri Räty wrote:
> It's an upstream bug and now I even got an url for it.
>
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6548443
>
> Regards,
> Petteri
>
--
gentoo-java@gentoo.org mailing list
prev parent reply other threads:[~2007-12-11 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 20:52 [gentoo-java] FYI in case you wondering why 1.6 needs libstdc++.so.5 Petteri Räty
2007-12-11 4:13 ` Calvin Austin [this message]
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=1197346419.6612.16.camel@localhost.localdomain \
--to=caustin@spikesource.com \
--cc=betelgeuse@gentoo.org \
--cc=gentoo-java@lists.gentoo.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