[Bug libstdc++/41816] ldconfig warnings vs. libstdc++.so.6.0.14-gdb.py

2014-03-22 Thread jvdelisle at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41816 Jerry DeLisle changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug libstdc++/41816] ldconfig warnings vs. libstdc++.so.6.0.14-gdb.py

2011-09-15 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41816 --- Comment #9 from Jonathan Wakely 2011-09-15 11:33:50 UTC --- Hmm yes, this is only really an issue for people who install libstdc++ into a directory that ldconfig searches, which for most people means it only affects the system compiler, which

[Bug libstdc++/41816] ldconfig warnings vs. libstdc++.so.6.0.14-gdb.py

2011-09-15 Thread markus at trippelsdorf dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41816 --- Comment #8 from Markus Trippelsdorf 2011-09-15 10:50:37 UTC --- (In reply to comment #7) > (In reply to comment #6) > > Why don't we just install this file in > > /usr/share/gdb/auto-load/usr/lib64/gcc/x86_64-pc-linux-gnu/4.7.0/ instead of >

[Bug libstdc++/41816] ldconfig warnings vs. libstdc++.so.6.0.14-gdb.py

2011-09-15 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41816 --- Comment #7 from Jonathan Wakely 2011-09-15 10:04:18 UTC --- (In reply to comment #6) > Why don't we just install this file in > /usr/share/gdb/auto-load/usr/lib64/gcc/x86_64-pc-linux-gnu/4.7.0/ instead of > $(DESTDIR)$(toolexeclibdir)/ by def

[Bug libstdc++/41816] ldconfig warnings vs. libstdc++.so.6.0.14-gdb.py

2011-09-15 Thread markus at trippelsdorf dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41816 Markus Trippelsdorf changed: What|Removed |Added CC||markus at trippelsdorf dot

[Bug libstdc++/41816] ldconfig warnings vs. libstdc++.so.6.0.14-gdb.py

2011-01-08 Thread rob1weld at aol dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41816 Rob changed: What|Removed |Added CC||rob1weld at aol dot com --- Comment #5 from Rob 20