This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [JAVA] /bin/sh portability issues in scripts/check_jni_methods.sh
- From: Roger Sayle <roger at eyesopen dot com>
- To: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- Cc: java-patches at gcc dot gnu dot org, <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 7 Jul 2006 07:25:01 -0600 (MDT)
- Subject: Re: [JAVA] /bin/sh portability issues in scripts/check_jni_methods.sh
On 7 Jul 2006, Rainer Orth wrote:
> 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
Cool! Yes, this exactly the issue and your patch above is nearly
identical to the one I have in my tree to allow the build to reach
libjava. Unfortunately, I'm seeing a unresolved symbol reference to
GC_register_has_static_roots_callback from libgcj.so when attempting
to link jv-convert, so I wasn't sure if it was my X86_64/SUNOS5 changes
in boehmgc/include/private/gcconfig.h that were at fault, or another
latent problem in the libjava build system.
Anyway, thanks again for pointing out that you're on top of this
particular issue (one less thing for me to worry about). Hopefully,
Hans will comment soon. I did check the upstream sources to see if
it was just an import of the latest boehmgc that was required.
Thanks again for addressing this.
Roger
--