[lsb-discuss] Building and checking a 3.0 compliant package under the 4.0 SDK

[Steve Goetze]

I did have a downlevel version - good catch.  I installed the latest
release of the SDK and was able to get "3.0" accepted as a version.

In my new appchk results, I still see two types of External Interfaces issues:

1.) Interfaces being pulled from libpthread.so.0 and marked as not in LSB 3.0:

Interface: read (GLIBC_2.2, libpthread.so.0)
LSB Status:
Never been in LSB.
Presence in Distributions
Present in:

    * CentOS 4.6
    * SLES 10

I think there may have been a post about this on the mailing list
earlier, and this error can be ignored - is that correct?

2.) Interfaces that are in LSB 3.0, but marked not present in the Distributions:

Interface: socket (GLIBC_2.2, libc.so.6)
LSB Status:
Mandatory since LSB 1.3.
Presence in Distributions
Missing in:

    * CentOS 4.6
    * SLES 10

These errors I don't understand.  FWIW, I get the same errors building
the package for LSB 4.0 and testing against the 4.0 level.

I would be happy to provide both sets of appchk results (3.0 and 4.0)
if it would be helpful.

Thanks again for your assistance,
--Steve Goetze

On Tue, Apr 14, 2009 at 8:02 AM, Stew Benedict
<stewb at linux-foundation.org> wrote:
> Steve Goetze wrote:
>>
>> It appears that "3.0" is not recognized, but "3.1" is:
>>
>> lsbuser at etpglrn:/usr/src/packages/SPECS> export LSBCC_LSBVERSION=3.0
>> lsbuser at etpglrn:/usr/src/packages/SPECS> /opt/lsb/bin/lsbc++
>> LSBCC_LSBVERSION is set to unrecognized value 3.0
>> lsbc++: no input files
>>
>> lsbuser at etpglrn:/usr/src/packages/SPECS> export LSBCC_LSBVERSION=3.1
>> lsbuser at etpglrn:/usr/src/packages/SPECS> /opt/lsb/bin/lsbc++
>> lsbc++: no input files
>>
>>
>>
>
> That sounds like http://bugs.linuxbase.org/show_bug.cgi?id=2485. I thought
> that had been fixed before 4.0 went final. Do you possibly have an older
> build of lsb-build-cc?
>
> --
> Stew Benedict
> Linux Foundation
>
>
>