From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#35529: libdrm fails to build on armhf-linux Date: Mon, 06 May 2019 19:00:12 +0200 Message-ID: <87a7fzfrhf.fsf@elephly.net> References: <87d0l1n97o.fsf@netris.org> <87k1f8gl7k.fsf@elephly.net> <87imuosew7.fsf@netris.org> <874l68qcio.fsf@elephly.net> <8736lsq9ec.fsf@netris.org> <8736lrrget.fsf@elephly.net> <87a7fz7cyq.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:55775) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNzVv-0000Dd-21 for bug-guix@gnu.org; Tue, 07 May 2019 08:48:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hNzVq-0001fj-0q for bug-guix@gnu.org; Tue, 07 May 2019 08:48:07 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44789) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hNzVp-0001fe-Qq for bug-guix@gnu.org; Tue, 07 May 2019 08:48:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hNzVp-0002OD-K8 for bug-guix@gnu.org; Tue, 07 May 2019 08:48:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87a7fz7cyq.fsf@netris.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 35529@debbugs.gnu.org Hi Mark, > Ricardo Wurmus 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=E2=80=99m not sure. We=E2=80=99re using a few Overdrive 1000 machin= es 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=E2=80=99t= 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=E2=80=99t know where I would find that information. >> =E2=80=9Cnss=E2=80=9D 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: . I didn=E2=80=99t 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. --=20 Ricardo