Re: Should we stop stripping static libraries?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 11 November 2016 12:46 AM, Florian Weimer wrote:
> We currently call /usr/lib/rpm/brp-strip-static-archive from
> %__os_install_post.  This removes debugging symbols from static (.a)
> libraries.
> 
> Is this really a good idea?  Due to this, glibc copies libc.a to
> glibc-debuginfo, so that you can get a link with debugging symbols by
> specifying “-static -L/usr/lib/debug/usr/lib64“ (potentially with
> unintended side effects).  I would like to get this to work by default.
> 
> If developers does not want debugging symbols and static libraries have
> them, they can link with -s, or strip the linked object.

What happens if a program built without -g is linked to the libc.a with
debug symbols?  If it does the right thing by not including debug
symbols then I think your suggestion is the right way forward.
Otherwise we need to fix the linker to not include debug symbols first.

Siddhesh
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux