unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 43513@debbugs.gnu.org
Subject: bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot
Date: Wed, 30 Sep 2020 11:10:17 +0200	[thread overview]
Message-ID: <87k0wb3a12.fsf@gnu.org> (raw)
In-Reply-To: <20200929124308.419282f2@scratchpost.org> (Danny Milosavljevic's message of "Tue, 29 Sep 2020 12:43:08 +0200")

Hi,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> On Tue, 29 Sep 2020 12:25:54 +0200
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> > I'd like to test what happens if one builds json-c on an aarch64 host
>> > for i686.
>> >
>> > Could we enable qemu-binfmt for i686 on an aarch64 host for me to test it?  
>> 
>> I think you can just run ‘qemu-i386 /path/to/your/program’; no need for
>> the whole binfmt_misc shebang.
>
> Sure, but I want to know what happens to json-c.  That sounds like a lot of
> manual invocations (like about 20000--for invocations of "configure", "gcc",
> including all the dependencies etcetc).

Do we know which bit of json-c’s ‘configure’ draws an incorrect
conclusion?

> Andreas Enge already tried to configure dover.guix.info to uses qemu-binfmt
> to emulate i686-linux, but apparently it doesn't work (on dover.guix.info):
>
> building /gnu/store/7wz8nqh6nkfqz6l780i6i34c6wa6ic6q-guile-bootstrap-2.0.drv...
> \builder for `/gnu/store/7wz8nqh6nkfqz6l780i6i34c6wa6ic6q-guile-bootstrap-2.0.drv' failed with exit code 1
> build of /gnu/store/7wz8nqh6nkfqz6l780i6i34c6wa6ic6q-guile-bootstrap-2.0.drv failed
> View build log at '/var/log/guix/drvs/7w/z8nqh6nkfqz6l780i6i34c6wa6ic6q-guile-bootstrap-2.0.drv.bz2'.
>
> bash-5.0$ bzless /var/log/guix/drvs/7w/z8nqh6nkfqz6l780i6i34c6wa6ic6q-guile-bootstrap-2.0.drv.bz2
> ------> /var/log/guix/drvs/7w/z8nqh6nkfqz6l780i6i34c6wa6ic6q-guile-bootstrap-2.0.drv.bz2 <------
> while setting up the build environment: executing `/gnu/store/mzfkrxd4w8vqrmyrx169wj8wyw7r8i37-bash': No such file or directory

That’s to little context for me to say much (I’d need to see the command
at least) but it could be that it’s trying to run i686 code on ARM or
similar.

Ludo’.




  parent reply	other threads:[~2020-09-30  9:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19 15:36 bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot Danny Milosavljevic
2020-09-19 21:05 ` Danny Milosavljevic
2020-09-21 12:22 ` Danny Milosavljevic
2020-09-21 12:23   ` Danny Milosavljevic
2020-09-21 12:44   ` Danny Milosavljevic
2020-09-25 10:13   ` Ludovic Courtès
2020-09-25 11:13     ` Danny Milosavljevic
2020-09-25 11:18       ` Danny Milosavljevic
2020-09-25 16:00         ` Ludovic Courtès
2020-09-25 16:25           ` Danny Milosavljevic
2020-09-26 10:53             ` Danny Milosavljevic
2020-09-26 17:20               ` Andreas Enge
2020-09-27  9:50               ` Andreas Enge
2020-09-27 11:32                 ` Danny Milosavljevic
2020-09-29 10:25               ` Ludovic Courtès
2020-09-29 10:43                 ` Danny Milosavljevic
2020-09-29 11:05                   ` Danny Milosavljevic
2020-09-30  9:10                   ` Ludovic Courtès [this message]
2020-09-30 11:27                     ` Danny Milosavljevic
2020-09-30 12:17                       ` Andreas Enge
2020-10-01 16:18                         ` Bengt Richter
2020-09-25 16:02       ` Ludovic Courtès
2020-09-25 16:23         ` Danny Milosavljevic
2020-09-25 16:37           ` Danny Milosavljevic

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=87k0wb3a12.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43513@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).