Broken libcc1 lookup in GDB/Ubuntu

[Luis Machado]

Hi,

While looking at enabling the compile tests in GDB's testsuite, I 
noticed GDB doesn't find the right shared library because it is looking 
for a different naming pattern.

In the case of Ubuntu 18.04/20.04, the shared library is named like so:

/usr/lib/aarch64-linux-gnu/libcc1.so.0.0.0
/usr/lib/aarch64-linux-gnu/libcc1.so.0 -> libcc1.so.0.0.0

But GDB is looking for libcc1.so in the following ways:

#define GCC_C_FE_LIBCC libcc1.so
#define GCC_CP_FE_LIBCC libcc1.so

So, basically, the gdb.compile tests will never be exercised 
out-of-the-box, even if you install the libcc1 package. I had to add a 
symlink named "libcc1.so" to make GDB happy.

Now, I noticed there was a proposed fix for this many years ago, in the 
following series:

https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01241.html
https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01242.html
https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01243.html
https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01244.html
https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01245.html

Was this dropped for some reason? Or is this still valid and should be 
pursued upstream?


Thanks,
Luis