Re: [libposix-development] trying to create a Debian package

[Henrique A. <hd...@gm...>]

2009/6/23 Aníbal Monsalve Salazar <an...@de...>:
>
> Thank you.

 No problem.

>
>
> That fixed my build problem.
>
> When do you plan to provide proper versioned symbols?

 It's a project goal to provide exactly one version of each function
at any moment. In principle symbol versions wouldn't be necessary. Is
this an unconditional requirement of Debian packages ?

>
> I would like to upload my package to Debian (Ubuntu will pick it up
> eventually) but I found some issues with the shared library. They are
> listed below.

 Note that currently libposix can only run one program (hello world).
It's in pre pre pre pre alpha state. :-) Is it safe to submit it to
Debian ?

 For the test below, it shows three problems:

 - The stack is flagged as executable
 - The library file name doesn't have a version
 - The library doesn't have dependency information

 The third problem is not a problem. The library doesn't depend on any
other library (it's statically linked).

 For the other two problems: I'm somewhat busy right now implementing
printf, so I won't be able to work on those soon. Can you deal with
them ? If that's not possible, please file bugs to the tracker, so
that we can track their progress.

 http://sourceforge.net/tracker/?group_id=261625

>
> lintian -i /tmp/libposix/libposix_0-1_i386.changes
> W: libposix-dev: shlib-with-executable-stack usr/lib/libposix.so
> N:
> N:    The listed shared libraries declares the stack as executable.
> N:
> N:    Executable stack is usually an error as it is only needed if the code
> N:    contains GCC trampolines or similar constructs which uses code on the
> N:    stack. One possible source for false positives are object files built
> N:    from assembler files which don't define a proper .note.GNU-stack
> N:    section.
> N:
> N:    To see the permissions on the stack, run readelf -l on the shared
> N:    library and look for the program header of type GNU_STACK. In the flag
> N:    column, there should not be an E flag set.
> N:
> W: libposix-dev: shlib-without-versioned-soname usr/lib/libposix.so libposix.so
> N:
> N:    The listed shared library in a public library directory has an SONAME
> N:    that does not contain any versioning information, either after the .so
> N:    or before it and set off by a hyphen. It cannot therefore be represented
> N:    in the shlibs system, and if linked by binaries its interface cannot
> N:    safely change. There is no backward-compatible way to migrate programs
> N:    linked against it to a new ABI.
> N:
> N:    Normally, this means the shared library is a private library for a
> N:    particular application and is not meant for general use. Policy
> N:    recommends that such libraries be installed in a subdirectory of
> N:    /usr/lib rather than in a public shared library directory.
> N:
> N:    To view the SONAME of a shared library, run readelf -d on the shared
> N:    library and look for the tag of type SONAME.
> N:
> N:    There are some special stub libraries or special-purpose shared objects
> N:    for which an ABI version is not meaningful. If this is one of those
> N:    cases, please add an override.
> N:
> N:    Refer to Debian Policy Manual section 10.2 (Libraries) and Debian Policy
> N:    Manual section 8.6 (Dependencies between the library and other packages
> N:    - the shlibs system) for details.
> N:
> W: libposix-dev: shared-lib-without-dependency-information ./usr/lib/libposix.so
> N:
> N:    The listed shared library doesn't include information about which other
> N:    libraries the library was linked against. (When running "ldd foo.so" ldd
> N:    should report about these other libraries. In your case, ldd just
> N:    reports "statically linked".)
> N:
> N:    To fix this, you should explicitly specify the libraries which are used
> N:    (e.g., "-lc") when building the shared library with "ld".
> N:
> N:    Severity: normal, Certainty: certain
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>



-- 
 Henrique Dante de Almeida
 hd...@gm...