> * Zbigniew Jędrzejewski-Szmek: > > > The general case of any statically linked code. It could be libgcc, > startup files, the non-shared bits of glibc, static-only libraries, or > header-only C++ libraries. > > Thanks, > Florian This would be indeed useful, but quite harder to do automagically I think? Is there rpmbuild magic that figures out that a static dependency is being used? If so, new fields could be used in the note section of the ELF object, eg: "staticLibfooName", "staticLibfooVersion", when the elf object is assembled. In the Debian world we have the Built-Using annotation that goes in the package metadata, I guess I'd use that as a source of info - but it does rely on the maintainer doing the manual annotation (for some languages like golang iirc it's done automatically, but we don't have anything for C/C++ iirc). _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
