libstdc++.so.6.0.*-gdb.py might be installed at the wrong place

[Basile STARYNKEVITCH <basile@starynkevitch.net>]

Hello

Sometimes, I am building & installing (on Linux/AMD64/Debian/Sid) the 
trunk configured as

/usr/src/Lang/gcc-trunk/configure  '--program-suffix=-trunk' 
'--libdir=/usr/local/lib/gcc-trunk' 
'--libexecdir=/usr/local/libexec/gcc-trunk' 
'--with-gxx-include-dir=/usr/local/lib/gcc-trunk/include/c++/' 
'--disable-multilib' '--enable-maintainer-mode' '--enable-languages=c,c++'

I don't know much the internals of libstdc++. But apparently, a file 
/usr/local/lib/lib64/libstdc++.so.6.0.12-gdb.py (refered as i 
/usr/local/lib/gcc-trunk/../lib64/libstdc++.so.6.0.12-gdb.py somehow) s 
installed and it seems to be a python script for some future version of gdb.

I would believe that it is the wrong place to install such a file. (In 
particular it makes ldconfig unhappy, when /usr/local/lib/lib64 is scanned).

Shouldn't a python script for gdb be installed  outside of a directory 
supposed to contain only  ELF libraries?  Wouldn't a gdb specific  
subdirectory be a more appropriate place?

And I am surprised it is in trunk. I thought that python support is for 
future GDB release (probably gdb 7.0, not yet released). Shouldn't such 
a script belong more to contrib? Why is it installed? Is there any 
synchronisation between gdb & gcc releases?

But I agree I don't know much about all that, and the installation part 
of the Makefile.in is something which still scares me a lot (in 
particular because I don't understand all the file path conventions).

Regards.

-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***