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 23:14:02 +0100 [thread overview]
Message-ID: <9f5b665a-dcec-0442-2e78-84d646c31e72@arm.com> (raw)
In-Reply-To: <YtXVUUxTMNeS2D6Z@wildebeest.org>
On 7/18/22 22:49, Mark Wielaard wrote:
> Hi Luis,
>
> On Mon, Jul 18, 2022 at 09:20:23AM +0100, Luis Machado wrote:
>>> 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.
>
> OK I checked and/or installed for:
>
> fedora-s390x expat-devel-2.4.7-1.fc36.s390x
> fedora-ppc64le expat-devel-2.4.7-1.fc36.ppc64le
> centos-x86_64 expat-devel-2.1.0-14.el7_9.x86_64
> debian-i386 libexpat1-dev-2.2.10-2+deb11u3
> debian-armhf libexpat1-dev-2.2.6-2+deb10u4
> debian-arm64 libexpat1-dev-2.2.6-2+deb10u4
>
> And the fedora and debian containers now got it added.
> opensuse containers already had libexpat-devel installed.
> (note how each distro calls the package by a slightly differnt name, sigh)
>
> Cheers,
>
> Mark
Thanks Mark. Yeah, unfortunately there is some naming variations.
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.
prev parent reply other threads:[~2022-07-18 22:14 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
2022-07-18 21:49 ` Mark Wielaard
2022-07-18 22:14 ` 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=9f5b665a-dcec-0442-2e78-84d646c31e72@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).