| Summary: | virtual/libiconv should have static-libs USE flag? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Julian Ospald <hasufell> |
| Component: | Current packages | Assignee: | Gentoo non-Linux Team <alt> |
| Status: | CONFIRMED --- | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 695878 | ||
|
Description
Julian Ospald
2015-09-30 10:42:42 UTC
(In reply to Julian Ospald (hasufell) from comment #0) > in order to propagate it to dev-libs/libiconv, no? +1 > I'm not sure what the state of the various libc providers is and if they > even consistently provide static libs, but there somehow should be a way to > properly do this. IMHO static-libs on libc, or any @system package, is a worm can: unless you want to kill implicit system deps, you can't [static-libs] usedep on them, so better always install them. Also, this'd prevent 'gcc -static' from working, since '-lc' is implicit and always passed to ld when linking; we also have packages building static binaries (busybox comes to mind) and thus relying on static libc.a. |
