[Bug 98] New: check_jni_methods.sh script fails on many systems
| Newsgroups | gmane.comp.java.vm.sablevm.bugs |
|---|---|
| Message-ID | <[email protected]> |
http://sablevm.org/bugs/show_bug.cgi?id=98
Summary: check_jni_methods.sh script fails on many systems
Product: SableVM
Version: unspecified
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: default
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
The script to check that all declared jni methods have in fact been defined works OK on Linux but fails
on many other systems.
Mostly this is due to sed not implementing the "\w" feature, but it seems that Mac OS X (10.3)
implements it but not in the way expected (==bug probably)). In some cases this can be worked around
but installing gsed but this still fails on Mac OS X.
At least one system (aix or solaris - I forget which rigt now) chokes on
TMPFILE=`mktemp`
as the mktemp implementation expects some arguments.
I'd like to pose the question of whether this activity is even appropriate in a stable distribution. If there
are classpath jni functions missing then the poor user is not able to do anything about it. I suggest that
this activity be done instead as part of the process of build-for-distribution, and not in the usual
sequence ./configure - make - make install
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.