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: Fri, 25 Sep 2020 18:02:54 +0200 [thread overview]
Message-ID: <87wo0hj13l.fsf@gnu.org> (raw)
In-Reply-To: <20200925131237.32fc61e9@scratchpost.org> (Danny Milosavljevic's message of "Fri, 25 Sep 2020 13:13:22 +0200")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Fri, 25 Sep 2020 12:13:40 +0200
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Let’s fix CMake (and JSON-C?) in ‘core-updates’ or ‘staging’ (using a
>> graft for CMake wouldn’t help because CMake is used at build time.)
>
> Sure--cmake upstream will fix it anyway and make a new release.
>
> But I now opened bug# 43591 on guix-patches in order to find all the OTHER
> problems this causes we didn't see yet. I already ran it on my laptop in
> order to find all the users trying to stick a 64-bit value into a 32-bit
> slot and it looks very bad--there are instances of this problem in libstdc++,
> binutils bfd etcetc.
Hmm, it’s this bad?
> I suggest to delete all ARM substitutes that were built on x86_64 machines
> and disable the builders using x86_64 to build ARM stuff in the mean time.
> What that has built is VERY MUCH not reliable since readdir() was broken
> sporadically--and compilers need that :P
What are the odds of a build succeeding in the presence of broken
getdents/readdir? Wouldn’t such builds simply fail (as in the CMake
case), as opposed to succeeding but somehow producing invalid binaries?
We can still disabled emulated builds on ci.guix.gnu.org, but let’s
first make sure we understand the practical impact of this bug.
> I thought this matter with making everyone use LFS was settled in about
> 2007--but no, here we go again :(
Yeah. :-/
Ludo’.
next prev parent reply other threads:[~2020-09-25 16:21 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
2020-09-30 12:17 ` Andreas Enge
2020-10-01 16:18 ` Bengt Richter
2020-09-25 16:02 ` Ludovic Courtès [this message]
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=87wo0hj13l.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).