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 19:00:12 +0200 [thread overview]
Message-ID: <87a7fzfrhf.fsf@elephly.net> (raw)
In-Reply-To: <87a7fz7cyq.fsf@netris.org>
Hi Mark,
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>>>>> 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.)
>
> So, many of the armhf builds are done in an emulator.
Since maybe a week or so. I only added the qemu machines very recently.
> I hope that we will soon phase out the practice of performing builds
> within emulators.
I did this because the extra Overdrive boxen I bought still haven’t been
added to the build farm. To better deal with the build backlog I added
the Qemu machines. I also hope that we can soon use dedicated build
machines instead.
> In the meantime, it would be good to know which machine built 'libdrm'
> for armhf. Was that information recorded?
I don’t know where I would find that information.
>> “nss” failed its tests when built on x15.sjd.se, but it worked fine when
>> building on one of the Overdrives.
>
> Can you find the failed NSS build log from the X15? It would useful to
> see which tests failed, and whether they're the same ones that failed on
> hydra-slave3, which is a Novena with 4 GB of RAM. Here's the relevant
> Hydra build page: <https://hydra.gnu.org/build/3484222>.
I didn’t keep track of the log. I built this manually on berlin to test
a workaround (which failed). The build log probably still sits on
berlin somewhere, but I cannot find it.
--
Ricardo
prev parent reply other threads:[~2019-05-07 12:48 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
2019-05-06 16:40 ` Mark H Weaver
2019-05-06 17:00 ` Ricardo Wurmus [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=87a7fzfrhf.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.