Re: FYI: lsb

[informer <informer@ns1.m2000.idv.tw>]

On Sun, 29 Apr 2001 thhsieh@tlug.sinica.edu.tw wrote:

> : [informer@ns1 bin]$ ./lsbappchk /usr/X11R6/lib/X11/xcin2.5/xcin
> : ./lsbappchk 0.8.0
> : Symbol _XRegisterFilterByType used, but not part of LSB
> : Symbol _XUnregisterFilter used, but not part of LSB
> : Symbol __finitef used, but not part of LSB
> : Symbol __finite used, but not part of LSB
> : Symbol __finitel used, but not part of LSB
> 
> 我剛剛去逛了一下，這個 project 是在測試程式是否符合 Linux
> 軟/硬體的標準嗎？

IMHO, software only 

I see you guys at linux.twbbs.org talk about portibility 

I think we can read LSB 
http://www.linuxbase.org/spec/
( I know Single UNIX Specification, but no utility available ... )

or use lsbdev package
http://www.linuxbase.org/usinglsbdev.html

> HP-UX B.10.XX, B.11.XX 系統 (也許還有 Solaris 系統, Darwin
> 系統？？)，都還沒遇到過問題，因此，也許我們還可以再「撐」一
> 段時間 :-))

thanks for the explanation
 
> 至於底下三個 __finitef 等 symbol 我就不清楚了，剛剛去搜尋一
> 下 xcin source tree 並沒有發現這三個東東。 LSB 的 imcompletement
> 嗎？ :-)))

maybe it's the fault from redhat6
even /bin/ls had some probelm :-)

[informer@ns1 informer]$ ./lsbappchk /bin/ls
./lsbappchk 0.8.0
Symbol __overflow used, but not part of LSB
Symbol __xstat64 has version GLIBC_2.1 expecting GLIBC_2.2
Symbol fnmatch has version GLIBC_2.0 expecting GLIBC_2.2.3
Symbol __lxstat64 has version GLIBC_2.1 expecting GLIBC_2.2
Symbol fwrite_unlocked used, but not part of LSB

--
Pofeng "informer" Lee, 李柏鋒, 886-928-554-335 ( 20:00-23:00 GMT+8 )
pofeng at linux.org.tw, an_evil_anti-opensource_nerd at PDAology.com.tw
Chang Gung Children's Hospital





To Unsubscribe: send mail to majordomo@linux.org.tw
with "unsubscribe xcin" in the body of the message