From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.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 13:27:54 +0200 [thread overview]
Message-ID: <20200930132754.1d88c9e2@scratchpost.org> (raw)
In-Reply-To: <87k0wb3a12.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Hi Ludo,
On Wed, 30 Sep 2020 11:10:17 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>
> > On Tue, 29 Sep 2020 12:25:54 +0200
> > Ludovic Courtès <ludo@gnu.org> wrote:
> > 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?
At least I don't. I don't even have a homedir on dover.guix.info, so I cannot
run guix pull, guix describe, or really anything that is interesting on there.
Andreas knows maybe--it works for him.
> > 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.
Note that /gnu/store/mzfkrxd4w8vqrmyrx169wj8wyw7r8i37-bash is an i686 executable
on dover.
Running it just like this
/gnu/store/mzfkrxd4w8vqrmyrx169wj8wyw7r8i37-bash
it works there on dover!
In order to reproduce the problem, you can log into dover.guix.info and then
run
guix build -s i686-linux json-c
.
Andreas knows more and can do much more on that machine.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-30 11:29 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
2020-09-30 11:27 ` Danny Milosavljevic [this message]
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=20200930132754.1d88c9e2@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=43513@debbugs.gnu.org \
--cc=ludo@gnu.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).