Closed Bug 570667 Opened 15 years ago Closed 15 years ago

"configure: error: The header jni.h was not found." for maemo tryserver build

Categories

(Release Engineering :: General, defect)

ARM
Maemo
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 570440

People

(Reporter: cjones, Unassigned)

Details

http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1275977603.1275978149.22539.gz Maemo try hg build on 2010/06/07 23:13:23 s: try-linux-slave03 ... checking for jar... : configure: error: The header jni.h was not found. Set $JAVA_HOME to your java sdk directory, use --with-java-bin-path={java-bin-dir}, or reconfigure with --disable-javaxpcom. *** Fix above errors and then restart with "make -f client.mk build" make[2]: *** [configure] Error 1 make[2]: Leaving directory `/scratchbox/users/cltbld/home/cltbld/build' make[1]: *** [/scratchbox/users/cltbld/home/cltbld/build/objdir/xulrunner/Makefile] Error 2 make[1]: Leaving directory `/scratchbox/users/cltbld/home/cltbld/build' make: *** [build] Error 2 I'm not aware of recent m-c changes that might have caused this but haven't been following closely.
It's possible that bug 557824 changed configure enough that the mozconfig for try is no longer good. That's at http://hg.mozilla.org/build/buildbot-configs/file/0bc1b04f3685/tryserver/mozconfig-maemo while the maemo5-gtk builds against mozilla-central are using a much shorter config of http://hg.mozilla.org/build/buildbot-configs/file/0bc1b04f3685/mozilla2/mobile/maemo5-gtk/mobile-browser/nightly/mozconfig jhford, could you take a look ?
I wonder why it is saying to use --disable-javaxpcom when it is used: http://hg.mozilla.org/build/buildbot-configs/file/tip/tryserver/mozconfig-maemo#l5 Is this happening on all maemo try server builds?
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.