From: Luis Machado <luis.machado@linaro.org>
To: Ruslan Kabatsayev <b7.10110111@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
jan.kratochvil@redhat.com, Jeff Law <law@redhat.com>
Subject: Re: Broken libcc1 lookup in GDB/Ubuntu
Date: Wed, 24 Mar 2021 13:55:46 -0300 [thread overview]
Message-ID: <6a506f33-c4c3-e893-e372-0e747a03f474@linaro.org> (raw)
In-Reply-To: <CAHEcG95O5sf9X9UangENA8WZ5veBCXf8Cr07wstbbJheCEQskg@mail.gmail.com>
On 3/24/21 1:45 PM, Ruslan Kabatsayev wrote:
> Hi,
>
> On Wed, 24 Mar 2021 at 18:15, Luis Machado via Gdb <gdb@sourceware.org> wrote:
>>
>> 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
>
> "apt-file search libcc1.so" shows me that e.g. gcc-9 package (and
> other versions of gcc) provides the suffixless version. It's installed
> as a symlink into /usr/lib/gcc/aarch64-linux-gnu/9/libcc1.so . Can it
> not be found?
>
Those do exist, but GDB seems to want to load that library from
/usr/lib/aarch64-linux-gnu, and not from, say,
/usr/lib/aarch64-linux-gnu/9/libcc1.so.
There is no symlink from /usr/lib/aarch64-linux-gnu/libcc1.so.0 pointing
at the version-specific file.
>>
>> 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
>
> Regards,
> Ruslan
>
prev parent reply other threads:[~2021-03-24 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 15:15 Luis Machado
2021-03-24 15:16 ` Luis Machado
2021-03-24 16:45 ` Ruslan Kabatsayev
2021-03-24 16:55 ` Luis Machado [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a506f33-c4c3-e893-e372-0e747a03f474@linaro.org \
--to=luis.machado@linaro.org \
--cc=b7.10110111@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=law@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).