From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Roger Sayle <roger@eyesopen.com>
Cc: java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [JAVA] /bin/sh portability issues in scripts/check_jni_methods.sh
Date: Fri, 07 Jul 2006 10:41:00 -0000 [thread overview]
Message-ID: <yddd5chlmtq.fsf@manam.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: Roger Sayle's message of "Thu, 6 Jul 2006 22:44:19 -0600 (MDT)"
Roger Sayle <roger@eyesopen.com> writes:
> terminating with a hard error, and enables libjava to reach the
> application linking steps at the end of the build (which suffer from
> boehmgc issues that I may not have resolved correctly).
This is probably PR boehm-gc/21942.
I've recently sent a new message about this to the boehm-gc list:
http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2006-June/001334.html
In the past, it was possible to get around boehm-gc test failures by
switching to pthreads on Solaris/x86 (though I vaguely recall that this
broke Solaris/SPARC). I'm still waiting for Hans to comment on my patch
and eventually make a copy of gc6.[89] which has made this switch available
for testing.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
next prev parent reply other threads:[~2006-07-07 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 5:06 Roger Sayle
2006-07-07 10:41 ` Rainer Orth [this message]
2006-07-07 13:47 ` Roger Sayle
2006-07-07 22:45 ` Solaris/X96 GC issues (was /bin/sh portability issues ...) Boehm, Hans
2006-07-07 22:49 ` Solaris/X86 " Boehm, Hans
2006-07-10 12:22 ` Solaris/X96 " Rainer Orth
2006-07-08 0:31 ` [JAVA] /bin/sh portability issues in scripts/check_jni_methods.sh Mike Stump
2006-07-08 0:51 ` Ralf Wildenhues
2006-07-08 0:57 ` Andrew Pinski
2006-07-08 1:05 ` Ralf Wildenhues
2006-08-18 19:54 ` Tom Tromey
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=yddd5chlmtq.fsf@manam.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=roger@eyesopen.com \
/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).