Closed
Bug 488168
Opened 16 years ago
Closed 16 years ago
XULRunner build bustage on FreeBSD (in javaxpcom)
Categories
(Toolkit Graveyard :: XULRunner, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9.2a1
People
(Reporter: mpk, Assigned: mpk)
References
Details
Attachments
(2 files)
849 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
729 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
ULRunner trunk builds on FreeBSD broke a few days ago (maybe since the
landing of bug 485984). The build stops with the following message
(truncated for better legibility):
...
gmake[5]: Entering directory `/work/build/xulrunner/extensions/java/xpcom/src'
nsAppFileLocProviderProxy.cpp
...
In file included from ../../../../dist/include/system_wrappers/jni.h:3,
from /work/src/mozilla/extensions/java/xpcom/src/nsAppFileLocProviderProxy.h:42,
from /work/src/mozilla/extensions/java/xpcom/src/nsAppFileLocProviderProxy.cpp:38:
/usr/local/java/include/jni.h:27:20: error: jni_md.h: No such file or directory
...
gmake[5]: *** [nsAppFileLocProviderProxy.o] Error 1
gmake[5]: Leaving directory `/work/build/xulrunner/extensions/java/xpcom/src'
...
Attachment #372451 -
Flags: review?(benjamin)
Updated•16 years ago
|
Attachment #372451 -
Flags: review?(benjamin) → review+
Assignee | ||
Updated•16 years ago
|
Keywords: checkin-needed
Assignee | ||
Comment 1•16 years ago
|
||
The makefile for the javaxpcom glue needs the same tweak as well.
Those two patches combined solve the javaxpcom build bustage on FreeBSD.
Please note that bug 487960 still prevents you from building XULRunner
from trunk, but that's another issue that has to be tackled separately.
Attachment #372811 -
Flags: review?(benjamin)
Updated•16 years ago
|
Attachment #372811 -
Flags: review?(benjamin) → review+
Comment 2•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.2a1
Updated•9 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•