I wonder if any version of gpc for linux is compliant or conformant with the Linux Standard Base. When I run your hello program through their lsbappchk it gives messages like this:
FAIL Symbol isnanl is used, but is not included in LSB 3.2 (Core & C++ & Desktop)
Yang Lao wrote:
I wonder if any version of gpc for linux is compliant or conformant with the Linux Standard Base. When I run your hello program through their lsbappchk it gives messages like this:
FAIL Symbol isnanl is used, but is not included in LSB 3.2 (Core & C++ & Desktop)
I belive that short answer in no. Longer answer: IIUC Linux Standard Base is a _binary_ specification. "Canonical" gpc distribution is in source form. In particular configure/build process is supposed to discover and use capabilities of the target platform. So one way to get LSB compliant gpc would be to compile gpc on "true" LSB system -- that is system which provides all LSB specified capabilities and nothing more.
If you want to deliver LSB compliant application simpler way may be to statically link all functions not included in LSB.
On Mon, Jun 2, 2008 at 2:15 PM, Waldek Hebisch hebisch@math.uni.wroc.pl wrote:
Yang Lao wrote:
I wonder if any version of gpc for linux is compliant or conformant with the Linux Standard Base. When I run your hello program through their lsbappchk it gives messages like this:
FAIL Symbol isnanl is used, but is not included in LSB 3.2 (Core & C++ &
Desktop)
I belive that short answer in no. Longer answer: IIUC Linux Standard Base is a _binary_ specification. "Canonical" gpc distribution is in source form. In particular configure/build process is supposed to discover and use capabilities of the target platform. So one way to get LSB compliant gpc would be to compile gpc on "true" LSB system -- that is system which provides all LSB specified capabilities and nothing more.
Has anyone estimated whether this is feasible?
-
Waldek Hebisch -
Yang Lao