From: Luis Machado <luis.machado@arm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org
Subject: Re: Fedora arm64 packages for gdb testing
Date: Mon, 18 Jul 2022 09:20:23 +0100 [thread overview]
Message-ID: <fa603c35-f130-75d9-f342-9e171dc045c3@arm.com> (raw)
In-Reply-To: <20220717163912.GB1558@gnu.wildebeest.org>
On 7/17/22 17:39, Mark Wielaard wrote:
> Hi Luis,
>
> On Fri, Jul 15, 2022 at 01:05:15PM +0100, Luis Machado wrote:
>> I noticed the Fedora arm64 worker for GDB is not running the tests
>> properly. This is due to a missing libexpat.
>>
>> There might be other packages missing, but for now libexpat should
>> make the g> db tests work fine.
>
> I installed expat-devel on the machine and this does indeed seem to
> have turned the tests using the gdbserver target green.
>
> https://sourceware.org/pipermail/gdb-testers/2022q3/171821.html
>
> I noticed libexpat-devel isn't installed on other builders. Is it only
> necessary on arm? Or should we make sure it is always installed?
It may be the case that other targets don't rely as much on XML descriptions as the Arm port does.
I'd recommend always installing libexpat on the builders to get the best outcome.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2022-07-18 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 12:05 Luis Machado
2022-07-17 16:39 ` Mark Wielaard
2022-07-18 8:20 ` Luis Machado [this message]
2022-07-18 21:49 ` Mark Wielaard
2022-07-18 22:14 ` Luis Machado
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=fa603c35-f130-75d9-f342-9e171dc045c3@arm.com \
--to=luis.machado@arm.com \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
/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).