From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Cc: Robert Schuster <robertschuster@fsfe.org>,
Henning Heinold <h.heinold@tarent.de>
Subject: Weird build problem with classpath-native/java-initial
Date: Thu, 20 Sep 2012 08:39:15 +0200 [thread overview]
Message-ID: <505ABA13.2050109@dresearch-fe.de> (raw)
We hit a weird build problem after upgrading from openSUSE 12.1 to 12.2.
We're building oe-classic (2011.03-maintenance). But the problem may be relevant for oe-core/meta-java too.
The first observation was that the do_configure step of classpath-native did not finish.
-------------> bitbake output <----------------
...
NOTE: Running task 7 of 18 (ID: 12, /home/sledz/work/openembedded/recipes/classpath/classpath-native_0.98.bb, do_configure)
NOTE: package classpath-native-0.98-r4: task do_configure: Started
(no more output here)
---------------------------------------------------------------------------------------------
Some investigations later we learned that configure calls a self built java-initial script. This script seams to have a problem.
-------------> config.log <---------------
configure:23774: checking if /home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial works
configure:23805: CLASSPATH=.: /home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial Test
/home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial: line 14: 9173 Segmentation fault jamvm-initial ${1+"$@"}
/home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial: line 14: 9178 Segmentation fault jamvm-initial ${1+"$@"}
/home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial: line 14: 9183 Segmentation fault jamvm-initial ${1+"$@"}
/home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial: line 14: 9188 Segmentation fault jamvm-initial ${1+"$@"}
/home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial: line 14: 9193 Segmentation fault jamvm-initial ${1+"$@"}
/home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial: line 14: 9198 Segmentation fault jamvm-initial ${1+"$@"}
...
---------------------------------------------------------------------------------------------
A short look into this script shows the cause for the endless loop.
-------------> /home/sledz/work/HydraIP/OE/tmp.6/sysroots/i686-linux/usr/bin/java-initial <---------------
#!/bin/sh
#
# Wrapper which (almost) silently restarts the VM in case of segfaults.
redo_from_start=1;
while [ $redo_from_start -eq 1 ]; do
echo "Running JamVM-initial: ${@}"
redo_from_start=0;
jamvm-initial ${1+"$@"}
if [ $? -eq 139 ]; then
echo "JamVM-initial crashed - silently trying again"
redo_from_start=1;
fi
done
---------------------------------------------------------------------------------------------
I see two problems:
* First the script should not use an endless loop.
* Second the segfault should be fixed.
Any specialists with suggestions handling this?
Regards,
Steffen
BTW: I'm absolutely not a Java specialist.
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next reply other threads:[~2012-09-20 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 6:39 Steffen Sledz [this message]
2012-10-02 13:53 ` [2011.03-maintenance 0/2] pull request 20121002 Steffen Sledz
2012-10-02 13:53 ` [2011.03-maintenance 1/2] jamvm: reorganize metadata to simplify backport from meta-java Steffen Sledz
2012-10-02 13:53 ` [2011.03-maintenance 2/2] jamvm-initial: backport 1.4.5 " Steffen Sledz
2012-10-09 14:40 ` [2011.03-maintenance 0/2] pull request 20121002 Tom Rini
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=505ABA13.2050109@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=h.heinold@tarent.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=robertschuster@fsfe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.