[Bug binutils/15920] not suitable as a general-purpose header
https://sourceware.org/bugzilla/show_bug.cgi?id=15920 Earnie Boyd changed: What|Removed |Added CC||earnie at users dot sourceforge.ne ||t --- Comment #2 from Earnie Boyd --- I agree with Andreas. I think the bug is that MinGW is providing the header and library as general purpose. However, another issue is that at least in binutils there is a --enable-install-libbfd configure option which installs the library as general purpose. Perhaps this issue needs to look at removing that option to prevent a general purpose install. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/15920] not suitable as a general-purpose header
https://sourceware.org/bugzilla/show_bug.cgi?id=15920 --- Comment #5 from Earnie Boyd --- Gdb also installs libbfd, libiberty and libopcodes all three are private libraries. Only libbfd adds a guard to protect against not having an autoconf config.h included before it. Why are these private development libraries being installed into publicly used space? Should they not remain private to the package and require being configured and compiled? It isn't like the package will check to see if the library exists in public, on the contrary it will always use the in-source versions without an option to do otherwise. So the bug with the packages is the installation of the private libraries into public space. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/15920] not suitable as a general-purpose header
https://sourceware.org/bugzilla/show_bug.cgi?id=15920 --- Comment #10 from Earnie Boyd --- What about my comment that the bug is the private libraries install into public space? If the private libraries are supposed to remain private why do they have an install target? If you install into public space then you need to allow the header to be used publicly. The issue isn't resolved because of the installation of supposed private library into public space. Please relabel this issue and consider the fact that installing a private library into public space is a bug that needs resolution. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
