From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: 35529@debbugs.gnu.org
Subject: bug#35529: libdrm fails to build on armhf-linux
Date: Mon, 06 May 2019 13:06:18 +0200 [thread overview]
Message-ID: <8736lrrget.fsf@elephly.net> (raw)
In-Reply-To: <8736lsq9ec.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> Ricardo Wurmus <rekado@elephly.net> writes:
>>>
>>>> Mark H Weaver <mhw@netris.org> writes:
>>>>
>>>>> Hydra failed two consecutive attempts to build libdrm on armhf-linux:
>>>>>
>>>>> https://hydra.gnu.org/build/3481547#tabs-summary
>>>>>
>>>>> Both build attempts were made on hydra-slave2, which is a Wandboard Quad
>>>>> based on the Freescale i.MX6 SOC.
>>>>
>>>> This has built fine on berlin. We have a completed build for
>>>> /gnu/store/3c28p8b07709isd9jlcnnnyrpgz4ndz8-libdrm-2.4.97.
>>>
>>> What kind of hardware was it built on?
>>
>> I’m not sure. We’re using a few Overdrive 1000 machines that have quite
>> a bit more RAM than the other armhf nodes.
>
> Are there any other kinds of build slaves that build armhf binaries for
> Berlin?
Yes. We have a Beagleboard (x15.sjd.se), which is set up for 2 parallel
builds and we use the Qemu service on 5 of our x86_64 machines to build
for armhf. (We do the same for aarch64, but using 5 different nodes.)
“nss” failed its tests when built on x15.sjd.se, but it worked fine when
building on one of the Overdrives.
--
Ricardo
next prev parent reply other threads:[~2019-05-06 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 21:41 bug#35529: libdrm fails to build on armhf-linux Mark H Weaver
2019-05-03 5:29 ` Ricardo Wurmus
2019-05-05 17:42 ` Andreas Enge
2019-05-05 22:41 ` Mark H Weaver
2019-05-06 7:15 ` Ricardo Wurmus
2019-05-06 8:22 ` Mark H Weaver
2019-05-06 11:06 ` Ricardo Wurmus [this message]
2019-05-06 16:40 ` Mark H Weaver
2019-05-06 17:00 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736lrrget.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35529@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).