Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#46324 - [attr] ship the static library
Attached to Project:
Arch Linux
Opened by David Kahles (flyingDavid) - Thursday, 17 September 2015, 14:15 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 20 September 2015, 03:36 GMT
Opened by David Kahles (flyingDavid) - Thursday, 17 September 2015, 14:15 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 20 September 2015, 03:36 GMT
|
DetailsDescription:
When building a static linked executable (in my case "dar"), the static library is required. This is e.g. the case when building executables for backup recovery, where you want to be independent of any libraries of the base live-system (less error-prone). |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 20 September 2015, 03:36 GMT
Reason for closing: None
Additional comments about closing: User requested: The user should rebuild the needed packages himself with staticlibs enabled.
Sunday, 20 September 2015, 03:36 GMT
Reason for closing: None
Additional comments about closing: User requested: The user should rebuild the needed packages himself with staticlibs enabled.
Comment by David Kahles (flyingDavid) -
Thursday, 17 September 2015, 15:06 GMT
After further reading I think the arch way is that the user rebuilds the needed packages himself. Sorry for the noise...