GNU bug report logs -
#29402
Failure to cross-compile GNU Hello for armhf-linux target
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29402 in the body.
You can then email your comments to 29402 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#29402
; Package
guix
.
(Wed, 22 Nov 2017 16:59:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Chris Marusich <cmmarusich <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 22 Nov 2017 16:59:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi,
On my x86_64 GuixSD machine, using Guix commit
77f921587c6b784e84b98a9f2e9c821f73114340, GNU Hello fails to build for
the armhf-linux target. It builds for the i686-linux, aarch64-linux,
and mip64el-linux targets.
I'm trying to build it using the following command, invoked from the
Guix source tree:
./pre-inst-env guix build --no-substitutes --target=armhf-linux hello
Here are the last few lines of output:
--8<---------------cut here---------------start------------->8---
starting phase `configure'
source directory: "/tmp/guix-build-binutils-cross-armhf-linux-2.28.drv-0/binutils-2.28" (relative from build: ".")
build directory: "/tmp/guix-build-binutils-cross-armhf-linux-2.28.drv-0/binutils-2.28"
configure flags: ("CONFIG_SHELL=/gnu/store/kpxi8h3669afr9r1bgvaf9ij3y4wdyyn-bash-minimal-4.4.12/bin/bash" "SHELL=/gnu/store/kpxi8h3669afr9r1bgvaf9ij3y4wdyyn-bash-minimal-4.4.12/bin/bash" "--prefix=/gnu/store/gaap2chgcwkhk6z0vp4z47cy6rsxds1q-binutils-cross-armhf-linux-2.28" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" "--target=armhf-linux" "--with-sysroot=/" "LDFLAGS=-static-libgcc" "--with-lib-path=/no-ld-lib-path" "--enable-install-libbfd" "--enable-deterministic-archives")
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... Invalid configuration `armhf-linux': machine `armhf' not recognized
configure: error: /gnu/store/kpxi8h3669afr9r1bgvaf9ij3y4wdyyn-bash-minimal-4.4.12/bin/bash ./config.sub armhf-linux failed
phase `configure' failed after 0.2 seconds
builder for `/gnu/store/3gqs8b7ch1w8xsc2adjnn8v7gm2ls8s1-binutils-cross-armhf-linux-2.28.drv' failed with exit code 1
@ build-failed /gnu/store/3gqs8b7ch1w8xsc2adjnn8v7gm2ls8s1-binutils-cross-armhf-linux-2.28.drv - 1 builder for `/gnu/store/3gqs8b7ch1w8xsc2adjnn8v7gm2ls8s1-binutils-cross-armhf-linux-2.28.drv' failed with exit code 1
cannot build derivation `/gnu/store/qhqngzgc0q7c1s3l25sm5y7mhqp99ciy-hello-2.10.drv': 1 dependencies couldn't be built
guix build: error: build failed: build of `/gnu/store/qhqngzgc0q7c1s3l25sm5y7mhqp99ciy-hello-2.10.drv' failed
--8<---------------cut here---------------end--------------->8---
It looks like the configure phase of the derivation that builds
binutils-cross-armhf-linux-2.28 failed because "armhf" is supposedly not
a recognized machine. However, "armhf-linux" is listed as a supported
platform in the Guix manual ((guix) GNU Distribution), so I expected
this to work. What's going on here?
GNU Hello successfully builds on my machine for the x86_64-linux,
i686-linux, aarch64-linux, and mips64el-linux platforms (i.e., all of
the other platforms listed as supported in the Guix manual).
--
Chris
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#29402
; Package
guix
.
(Thu, 23 Nov 2017 11:14:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 29402 <at> debbugs.gnu.org (full text, mbox):
Hi Chris,
Chris Marusich <cmmarusich <at> gmail.com> skribis:
> I'm trying to build it using the following command, invoked from the
> Guix source tree:
>
> ./pre-inst-env guix build --no-substitutes --target=armhf-linux hello
[...]
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... Invalid configuration `armhf-linux': machine `armhf' not recognized
The argument to --target must be a GNU triplet, not a Guix “system
type.”
GNU triplets have the form CPU-VENDOR-OS, which often looks like
CPU-KERNEL-OSABI. In this case, you want
--target=arm-linux-gnueabihf
HTH!
Ludo’.
Reply sent
to
Chris Marusich <cmmarusich <at> gmail.com>
:
You have taken responsibility.
(Fri, 24 Nov 2017 00:53:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Chris Marusich <cmmarusich <at> gmail.com>
:
bug acknowledged by developer.
(Fri, 24 Nov 2017 00:53:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 29402-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
ludo <at> gnu.org (Ludovic Courtès) writes:
> The argument to --target must be a GNU triplet, not a Guix “system
> type.”
Ah, I see! Thank you. When I tried again using the target you
suggested, it worked.
I have some follow-up questions, so I've sent a a follow-up email to
guix-devel.
--
Chris
[signature.asc (application/pgp-signature, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 22 Dec 2017 12:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 7 years and 178 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.