[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 --- Comment #7 from Martin Liska --- Thank you for the fix, looks fine now. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 Vladimir Mezentsev changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Vladimir Mezentsev --- Fixed in the master and binutils-2_40-branch branches. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 Kurt Goebel changed: What|Removed |Added Status|NEW |ASSIGNED CC||kurt.goebel at oracle dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The binutils-2_40-branch branch has been updated by Vladimir Mezentsev : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=edd36b26f3506eeb259534ba2493e15c728cd280 commit edd36b26f3506eeb259534ba2493e15c728cd280 Author: Vladimir Mezentsev Date: Wed Jan 25 19:21:38 2023 -0800 gprofng: PR30043 libgprofng.so.* are installed to a wrong location gprofng/ChangeLog 2023-01-25 Vladimir Mezentsev PR gprofng/30043 PR gprofng/28972 * src/Makefile.am: Use lib_LTLIBRARIES instead of pkglib_LTLIBRARIES. * src/Makefile.in: Rebuild. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Vladimir Mezentsev : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2b304f501f1fe7ca0a27a6e672fd9cf8f289b4eb commit 2b304f501f1fe7ca0a27a6e672fd9cf8f289b4eb Author: Vladimir Mezentsev Date: Wed Jan 25 19:21:38 2023 -0800 gprofng: PR30043 libgprofng.so.* are installed to a wrong location gprofng/ChangeLog 2023-01-25 Vladimir Mezentsev PR gprofng/30043 PR gprofng/28972 * src/Makefile.am: Use lib_LTLIBRARIES instead of pkglib_LTLIBRARIES. * src/Makefile.in: Rebuild. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 Sam James changed: What|Removed |Added CC||sam at gentoo dot org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 Sam James changed: What|Removed |Added See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=28972 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 --- Comment #3 from Michael Matz --- Proper shared libraries (those which programs link against via DT_NEEDED) have to be placed in directories in which the dynamic linker searches for them. You can play games with DT_RUNPATH of course but that would not be the normal action. So, shared libraries need to be placed in $(libdir). What you are talking about are dynamic modules: ELF DSOs intended for dlopen, i.e. to be loaded at runtime. Usually the difference is already visual in the filenames: shared libs have major.minor.micro version files and the foobar.so file is a symlink. Modules have just the .so file (and are usually not named 'lib*', though that's a convention not always followed). So the DSOs you create for modules (the collector stuff) indeed is properly placed into $(pkglibdir), but the shared library libgprofng.so.0 (which we know is one because the gprofng binary links against it) needs to be put into $(libdir). I don't know why H.J. suggested to put it into $(pkglibdir) but it's an incorrect advise. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 Martin Liska changed: What|Removed |Added Status|WAITING |NEW --- Comment #2 from Martin Liska --- (In reply to Vladimir Mezentsev from comment #1) > This is not a bug. Not all binutils libraries are installed in $(libdir). > See, for example, /tmp/install-libdir/bfd-plugins/ in your installation. Yes, I would expect something similar for gprofng, where /tmp/install-libdir/gprofng/libgp-iotrace.so /tmp/install-libdir/gprofng/libgp-sync.so /tmp/install-libdir/gprofng/libgp-heap.so /tmp/install-libdir/gprofng/libgp-collectorAPI.so /tmp/install-libdir/gprofng/libgp-collector.so are similar to bfd-plugins, while the main library should be places in $(libdir): /tmp/install-libdir/libgprofng.so /tmp/install-libdir/libgprofng.so.0 /tmp/install-libdir/libgprofng.so.0.0.0 similarly to e.g. libctf.so.0.0.0. Does it make sense? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30043] libgprofng.so.* are installed to a wrong location
https://sourceware.org/bugzilla/show_bug.cgi?id=30043 Vladimir Mezentsev changed: What|Removed |Added Status|NEW |WAITING --- Comment #1 from Vladimir Mezentsev --- This is not a bug. Not all binutils libraries are installed in $(libdir). See, for example, /tmp/install-libdir/bfd-plugins/ in your installation. We install the gprofng libraries in $(pkglibdir). See Bug 28972 - gprofng libraries should be installed under $(pkglibdir): H.J. Lu 2022-03-16 17:21:03 UTC Currently gprofng libraries are installed under $(libdir). I believe that they should be installed under $(pkglibdir). Can we close this bug as RESOLVED/NOTABUG ? -- You are receiving this mail because: You are on the CC list for the bug.
