<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3268" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=003281216-10042008><FONT face=Arial
color=#0000ff size=2>In informal discussion this morning, we talked about doing
an experiment with a buildable version of openjdk to find out if perhaps some of
the issues are easily eliminatable, and esp. if we can identify why syscall in
particular is being used. This would give an easier position to go to jre
vendors with the request meet midway on changes.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=003281216-10042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
lsb-discuss-bounces@lists.linux-foundation.org
[mailto:lsb-discuss-bounces@lists.linux-foundation.org] <B>On Behalf Of
</B>Alexey Khoroshilov<BR><B>Sent:</B> Thursday, April 10, 2008 10:12
AM<BR><B>To:</B> lsb-discuss@lists.linux-foundation.org<BR><B>Subject:</B> Re:
[lsb-discuss] LSB 3.2 Compliance Report: Sun JRE 6 (update 5) on
x86<BR></FONT><BR></DIV>
<DIV></DIV><TT>Alexey Khoroshilov wrote:</TT>
<BLOCKQUOTE cite=mid:47FC6429.3010501@ispras.ru type="cite"><TT>Please find
attached a report on LSB 3.2 Compliance of Sun JRE 6 (update 5) package for
x86. <BR><BR>Hopefully it can help us with discussions on getting LSB
compliant JRE and expansion of the standard. <BR></TT></BLOCKQUOTE><TT>Let me
summarize the report on getting LSB compliant Sun JRE.<BR><BR>The report
identifies several action items to be done by the LSB Workgroup. At the same
time the goal is not feasible without help from the side of the JRE development
team.<BR><BR>The action items for the LSB Workgroup are as
follows:<BR><B>AI-1-1.</B> Consider possibilities to add into LSB 4.0 the
interfaces required by Sun JRE. <BR>
If necessary initiate discussion with </TT><TT>the JRE development team</TT><TT>
on alternative solutions<B>.<BR>AI-1-2.</B> Define LSB position regarding to
pthread interfaces in libc.<BR><B>AI-1-3.</B> Investigate problems with ELF
sections detected by
lsb-appchk:<BR> - Section
.eh_frame: sh_flags is wrong. expecting 2, got
3<BR> - Section
.gcc_except_table: sh_flags is wrong. expecting 2, got
3<BR> - Dynamic Tag
0x6ffffffb unknown<BR><B>AI-1-4.</B> Investigate problems with RPM packaging in
light of RPM specification uplift.<BR><BR>The action items for the JRE
development team are as follows:<BR><B>AI-2-1.</B> Escape of superfluous library
dependencies. If it is impossible report the reasons.<BR><B>AI-2-2.</B> Consider
possibilities to replace usage of syscall()
interface.<BR> Provide us details if
it is not possible.<BR><B>AI-2-3.</B> Investigate possibilities to eliminate
dependincies on isnanf, atexit, __ctype_b, __ctype_tolower and __ctype_toupper.
The alternatives are __isnanf, __cxa_atexit, __ctype_b_loc, __ctype_tolower_loc
and __ctype_toupper_loc correspodingly.<BR><B>AI-2-4.</B> Investigate
possibilities to eliminate dependincies on __snd_* interfaces by using snd_*
analogues.<BR><B>AI-2-5.</B> Make sure that usage of ioctl() and dlopen()
satisfies to LSB requirements.<BR><B>AI-2-6.</B> Change installation location
from /usr/java/jre1.6.0_05 to /opt/[sun|java]/jre1.6.0_05 according to
FHS.<BR><B>AI-2-7.</B> (opt) Consider LSB recommendations on usage obsolete
interfaces.<BR><BR>Comments are welcome.<BR><BR>-- <BR>Regards, <BR>Alexey
<BR><BR></TT></BODY></HTML>