bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-10-01 Thread Bengt Richter
Hi, On +2020-09-30 14:17:31 +0200, Andreas Enge wrote: > Hello, > > On Wed, Sep 30, 2020 at 01:27:54PM +0200, Danny Milosavljevic wrote: > > 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

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-30 Thread Andreas Enge
Hello, On Wed, Sep 30, 2020 at 01:27:54PM +0200, Danny Milosavljevic wrote: > 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. this is a problem I have now seen at least three times, so

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-30 Thread Danny Milosavljevic
Hi Ludo, On Wed, 30 Sep 2020 11:10:17 +0200 Ludovic Courtès wrote: > Danny Milosavljevic skribis: > > > On Tue, 29 Sep 2020 12:25:54 +0200 > > Ludovic Courtès wrote: > > Sure, but I want to know what happens to json-c. That sounds like a lot of > > manual invocations (like about 2--for

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-30 Thread Ludovic Courtès
Hi, Danny Milosavljevic skribis: > On Tue, 29 Sep 2020 12:25:54 +0200 > Ludovic Courtès 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

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-29 Thread Danny Milosavljevic
On Tue, 29 Sep 2020 12:43:08 +0200 Danny Milosavljevic wrote: > /gnu/store/mzfkrxd4w8vqrmyrx169wj8wyw7r8i37-bash Also, this file exists, and is for i686, and if I invoke it using /gnu/store/mzfkrxd4w8vqrmyrx169wj8wyw7r8i37-bash -c "echo foo" then it works (which means the qemu transparent em

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-29 Thread Danny Milosavljevic
Hi Ludo, On Tue, 29 Sep 2020 12:25:54 +0200 Ludovic Courtès 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/p

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-29 Thread Ludovic Courtès
Hi, Danny Milosavljevic skribis: > 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 sheba

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-27 Thread Danny Milosavljevic
Hmm, /home/dannym is missing there. I can log in but not pull. pgp84jG1Lx8Up.pgp Description: OpenPGP digital signature

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-27 Thread Andreas Enge
Hello Danny, On Sat, Sep 26, 2020 at 12:53:20PM +0200, Danny Milosavljevic 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? > One machine is enough--I'd just run > guix environm

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-26 Thread Andreas Enge
Hello Danny, On Sat, Sep 26, 2020 at 12:53:20PM +0200, Danny Milosavljevic wrote: > Could we enable qemu-binfmt for i686 on an aarch64 host for me to test it? I am working (or rather, the machine is compiling) to set it up on dover. When it is finished, I will keep you updated (it may take a whil

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-26 Thread Danny Milosavljevic
Hi Ludo, On Fri, 25 Sep 2020 18:25:42 +0200 Danny Milosavljevic wrote: > On Fri, 25 Sep 2020 18:00:05 +0200 > Ludovic Courtès wrote: > > > You’re listed in overdrive.scm in maintenance.git, so you must have > > access to overdrive1.guixsd.org:52522. > > Indeed, I do. > > Thanks! I'd like

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Danny Milosavljevic
Hi Ludo, On Fri, 25 Sep 2020 18:02:54 +0200 Ludovic Courtès wrote: > 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? I don't know wh

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Danny Milosavljevic
> [1] "man getdents64" does not list EOVERFLOW--at least not for me. I meant "man readdir" pgpEpS5Aus0P7.pgp Description: OpenPGP digital signature

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Danny Milosavljevic
Hi Ludo, On Fri, 25 Sep 2020 18:00:05 +0200 Ludovic Courtès wrote: > You’re listed in overdrive.scm in maintenance.git, so you must have > access to overdrive1.guixsd.org:52522. Indeed, I do. Thanks! pgpWrxC2H3B9V.pgp Description: OpenPGP digital signature

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Ludovic Courtès
Danny Milosavljevic skribis: > On Fri, 25 Sep 2020 12:13:40 +0200 > Ludovic Courtès 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

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Ludovic Courtès
Danny Milosavljevic skribis: > On Fri, 25 Sep 2020 13:13:22 +0200 > Danny Milosavljevic wrote: > >> I do not think the X86_32 compatibility layer works on aarch64, so now we >> have >> a problem. That means building stuff for ARMv7 on aarch64 is not reliable at >> all. > > Hmm. > > Could I hav

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Danny Milosavljevic
On Fri, 25 Sep 2020 13:13:22 +0200 Danny Milosavljevic wrote: > I do not think the X86_32 compatibility layer works on aarch64, so now we have > a problem. That means building stuff for ARMv7 on aarch64 is not reliable at > all. Hmm. Could I have access to a aarch64 build machine? Or am I abl

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Danny Milosavljevic
Hi Ludo, On Fri, 25 Sep 2020 12:13:40 +0200 Ludovic Courtès 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#

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-25 Thread Ludovic Courtès
Hi Danny! Danny Milosavljevic skribis: > I found the underlying cause of the problem with qemu transparent emulation: > > * qemu transparent emulator has 64 bit registers > * the thing it's emulating has 32 bit registers > * The glibc in the distro that is running in the emulator is using getden

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-21 Thread Danny Milosavljevic
> to have 64 bit offsets or 32 bit offsets[1]. Right now, from user space, that > is only possible via process personality flags. Or via CONFIG_X86_X32, which exposes extra syscalls ON x86_64 ONLY. I guess that would be better than nothing--although glibc would have to look seriously strange to

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-21 Thread Danny Milosavljevic
Kernel side: https://bugzilla.kernel.org/show_bug.cgi?id=205957 pgpI9XT5tluSL.pgp Description: OpenPGP digital signature

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-21 Thread Danny Milosavljevic
Hi, I found the underlying cause of the problem with qemu transparent emulation: * qemu transparent emulator has 64 bit registers * the thing it's emulating has 32 bit registers * The glibc in the distro that is running in the emulator is using getdents64 (on 32 bits!) and then (rightfully) check

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-19 Thread Danny Milosavljevic
More info: https://gitlab.kitware.com/cmake/cmake/-/issues/20568 https://gitlab.kitware.com/utils/kwsys/-/merge_requests/187 > Furthermore, I'd like to ask: Why is json-c a dependency in the first place ? Because of sdl2. I've removed sdl2 from the native-inputs of u-boot and added it to the n

bug#43513: json-c build failure (on armhf-linux) while trying to build u-boot

2020-09-19 Thread Danny Milosavljevic
Hello, there is a build failure in json-c: $ guix environment -s armhf-linux --pure u-boot-a20-olinuxino-micro [...] running 'cmake' with arguments ("../json-c-0.14" "-DCMAKE_BUILD_TYPE=RelWithDebInfo" "-DCMAKE_INSTALL_PREFIX=/gnu/store/yqaw63n8wmg7f2ncc24019z87m5cwhim-json-c-0.14" "-DCMAKE_IN