Re: About static libraries and Debian policy

[Ludovic Brenta <ludovic@ludovic-brenta.org>]

Dmitry A. Kazakov writes on comp.lang.ada:
> On Fri, 14 May 2010 22:38:30 +0200, Ludovic Brenta wrote:
>
>> Dmitry A. Kazakov writes:
>>> On Fri, 14 May 2010 20:43:27 +0200, Ludovic Brenta wrote:
>>>
>>>>>>> BTW, Why there should be no traceback when relocatable libraries are
>>>>>>> used?
>>>> 
>>>> Traceback is always available, either in symbolic or numeric form.  To
>>>> get the symbolic form, you need the -dbg package installed.
>>>
>>> I meant g-trasym.adb. In Fedora's gcc 4.4 it is in the static library, but
>>> absent in the shared. I don't understand why.
>> 
>> Maybe the Fedora maintainers can explain?
>
> From g-trasym.ads:
>
> "On all platforms except VMS, this package is not intended to be used
> within a shared library, symbolic tracebacks are only supported for the
> main executable and not for shared libraries. You should consider using
> gdb to obtain symbolic traceback in such cases."
>
> This reads to me: don't use in a shared library. Maybe they just followed
> this advice. I admit, I don't understand the text above. In particular,
> since any library is dead without the main executable, comparing them makes
> no sense to me.

To me this reads: do not call this from a shared library; however your
main program can call this even if it is in a shared libgnat.  There is
no technical reason why g-trasym.adb cannot be compiled with -fPIC and
included in a shared library.  For that matter, if we followed your
interpretation, g-trasym.adb should not be in a static library either.

-- 
Ludovic Brenta.