From: Mark Wielaard <mark@klomp.org>
To: Tom de Vries <tdevries@suse.de>, Simon Marchi <simark@simark.ca>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
buildbot@sourceware.org
Subject: Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware)
Date: Wed, 15 Jun 2022 16:38:51 +0200 [thread overview]
Message-ID: <b1298fee8144059aa1f9ad1ae8d618704ea99eda.camel@klomp.org> (raw)
In-Reply-To: <9576d8d18b533c753df75a2cdb6ca9d786d71ff3.camel@klomp.org>
Hi Tom,
On Wed, 2022-06-15 at 13:09 +0200, Mark Wielaard wrote:
> > I did wonder why the builder didn't catch this. I found out that
> > the
> > buildbot gdb-opensuseleap-x86_64 did't fail because the buildbot
> > builds
> > gdb without debuginfod support.
> >
> > Mark, is this something we want to fix?
> >
> > For opensuse it's package libdebuginfod-devel.
>
> Yep, that seems like a good idea. Should now be added to the
> opensuse-
> leap container.
Note that this didn't actually work. Although the package is now
installed:
builder@df808da35762:~/build> rpm -qa | grep debuginfod
libdebuginfod-devel-0.185-150400.3.35.x86_64
The configure test still fails:
configure:7009: checking whether to use debuginfod
configure:7011: result: auto
configure:7017: checking for libdebuginfod >= 0.179
configure:7024: $PKG_CONFIG --exists --print-errors "libdebuginfod >= 0.179"
configure:7027: $? = 0
configure:7041: $PKG_CONFIG --exists --print-errors "libdebuginfod >= 0.179"
configure:7044: $? = 0
configure:7069: gcc -o conftest -g -O2 -ldebuginfod conftest.c -ldl >&5
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -ldebuginfod
collect2: error: ld returned 1 exit status
The problem is:
builder@df808da35762:~/build> ls -lah /usr/lib64/libdebuginfod.so
lrwxrwxrwx 1 root root 22 May 7 23:06 /usr/lib64/libdebuginfod.so ->
libdebuginfod-0.185.so
builder@df808da35762:~/build> ls -lah /usr/lib64/libdebuginfod-0.185.so
ls: cannot access '/usr/lib64/libdebuginfod-0.185.so': No such file or
directory
Is that a opensuse leap packaging bug?
BTW. To debug such builder container issues you can use this IMHO handy
guide:
https://sourceware.org/git/?p=builder.git;a=blob;f=README_containers;hb=HEAD
> CC buildbot list, where you can propose such patches yourself if you
> notice anything else missing.
>
> Cheers,
>
> Mark
>
next prev parent reply other threads:[~2022-06-15 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YmbmguMq2Aq+BzAX@wildebeest.org>
[not found] ` <524b04b7-a78c-7aae-4605-b40f61e6830c@arm.com>
[not found] ` <YmhzY4c3pOPLRgSw@wildebeest.org>
[not found] ` <16fe426d-c436-f030-dc43-0e81e7f0e853@arm.com>
[not found] ` <20220428141957.GB23335@gnu.wildebeest.org>
[not found] ` <m3zgk5clif.fsf@fitzsim.org>
[not found] ` <20220428162803.GD23335@gnu.wildebeest.org>
[not found] ` <20220429200422.GB7305@gnu.wildebeest.org>
[not found] ` <20220501194445.GB30898@gnu.wildebeest.org>
[not found] ` <f12d07da-8692-5321-95e1-8b2fb5a84cf1@simark.ca>
[not found] ` <YnG8lzwMZwRn+wAo@wildebeest.org>
[not found] ` <28a953d1-9fdc-e4f7-18cc-0b7b1a4e88ea@suse.de>
2022-06-15 11:09 ` Mark Wielaard
2022-06-15 14:38 ` Mark Wielaard [this message]
2022-06-15 19:18 ` Martin Liška
2022-06-15 19:48 ` Mark Wielaard
2022-06-16 4:09 ` Martin Liška
2022-06-16 21:19 ` Mark Wielaard
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=b1298fee8144059aa1f9ad1ae8d618704ea99eda.camel@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tdevries@suse.de \
/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).