RE: analyse some failures in lsbsi-ppc64
"Wichmann, Mats D" <[email protected]> Thu, 17 Jun 2004 22:31:56 -0700
| Newsgroups | gmane.linux.lsb.implementation |
|---|---|
| Message-ID | <A06801158AE07847B27A52C1A074BC1D04C910CF@fmsmsx404.amr.corp.intel.com> |
This is a multi-part message in MIME format. --===============1932037025== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C454F5.DB71C790" This is a multi-part message in MIME format. ------_=_NextPart_001_01C454F5.DB71C790 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable >/tset/LSB.os/jump/getcontext/T.getcontext 1 FAIL >/tset/LSB.os/jump/getcontext/T.getcontext 2 FAIL >/tset/LSB.os/jump/makecontext/T.makecontext 1 UNRESOLVED >/tset/LSB.os/jump/makecontext/T.makecontext 2 UNRESOLVED >/tset/LSB.os/jump/makecontext/T.makecontext 3 UNRESOLVED >/tset/LSB.os/jump/setcontext/T.setcontext 1 UNRESOLVED When not define __ASSUME_NEW_RT_SIGRETURN_SYSCALL, getcontext, makecontext and setcontext will return ENOSYS. To define __ASSUME_NEW_RT_SIGRETURN_SYSCALL, the kernel should be later than 2.4.21. The current configure will define __LINUX_KERNEL_VERSION to 2.4.19. sysdeps/unix/sysv/linux/configure define arch_minimum_kernel (ppc64) to 2.4.19=20 =20 =20 =20 Is this something we need to change on the lsbsi side? If so, where? We build "kernel headers" from a much later kernel version, but I'm not sure that affects whatever this problem is.=20 ------_=_NextPart_001_01C454F5.DB71C790 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD> <BODY><FONT face=3DArial color=3D#0000ff size=3D2></FONT> <DIV dir=3Dltr align=3Dleft><BR><B><FONT=20 face=3DArial>>/tset/LSB.os/jump/getcontext/T.getcontext 1=20 FAIL</FONT></B><BR><B><FONT=20 face=3DArial>>/tset/LSB.os/jump/getcontext/T.getcontext 2=20 FAIL</FONT></B><BR><B><FONT=20 face=3DArial>>/tset/LSB.os/jump/makecontext/T.makecontext 1=20 UNRESOLVED</FONT></B><BR><B><FONT=20 face=3DArial>>/tset/LSB.os/jump/makecontext/T.makecontext 2=20 UNRESOLVED</FONT></B><BR><B><FONT=20 face=3DArial>>/tset/LSB.os/jump/makecontext/T.makecontext 3=20 UNRESOLVED</FONT></B><BR><B><FONT=20 face=3DArial>>/tset/LSB.os/jump/setcontext/T.setcontext 1=20 UNRESOLVED</FONT></B><BR>When not define = __ASSUME_NEW_RT_SIGRETURN_SYSCALL,=20 getcontext, makecontext and<BR>setcontext will return ENOSYS. To define=20 __ASSUME_NEW_RT_SIGRETURN_SYSCALL,<BR>the kernel should be later than = 2.4.21.=20 The current configure will define<BR>__LINUX_KERNEL_VERSION to = 2.4.19.<FONT=20 face=3DArial> sysdeps/unix/</FONT><FONT = face=3DArial>sysv/linux/configure define=20 </FONT><FONT face=3DArial>arch_minimum_kernel</FONT><BR><FONT = face=3DArial>(ppc64)=20 to 2.4.19<SPAN class=3D358343005-18062004><FONT color=3D#0000ff=20 size=3D2> </FONT></SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN=20 class=3D358343005-18062004></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN=20 class=3D358343005-18062004></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN=20 class=3D358343005-18062004></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN = class=3D358343005-18062004><FONT=20 color=3D#0000ff size=3D2>Is this something we need to change on the = lsbsi=20 side?</FONT></SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN = class=3D358343005-18062004><FONT=20 color=3D#0000ff size=3D2>If so, where? We build "kernel headers" = from a=20 much</FONT></SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN = class=3D358343005-18062004><FONT=20 color=3D#0000ff size=3D2>later kernel version, but I'm not sure that = affects=20 whatever</FONT></SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN = class=3D358343005-18062004><FONT=20 color=3D#0000ff size=3D2>this problem is.</FONT></SPAN></FONT><FONT = face=3DArial><SPAN=20 class=3D358343005-18062004> </SPAN></FONT></DIV></BODY></HTML> ------_=_NextPart_001_01C454F5.DB71C790-- --===============1932037025== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lsb-impl mailing list [email protected] http://mail.freestandards.org/mailman/listinfo/lsb-impl --===============1932037025==--