From: Maxime Devos <maximedevos@telenet.be>
To: Zacchaeus Scheffer <zaccysc@gmail.com>, 50858@debbugs.gnu.org
Subject: bug#50858: Installing git-annex for aarch64 fails on ghc build
Date: Fri, 01 Oct 2021 22:16:59 +0200 [thread overview]
Message-ID: <ccb0664d76de0e2cb0184dce5a633e917f6fb380.camel@telenet.be> (raw)
In-Reply-To: <CAJejy7=fnxBTUfP3YfHyeR6=wOFJ-rCHFnspP6rD+zz2R_G7Hw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Zacchaeus Scheffer schreef op ma 27-09-2021 om 18:28 [-0400]:
> Hi Guix!
>
> I'm trying to install git-annex for aarch64,
Are you doing --target=aarch64-linux-gnu or --system=aarch64-linux?
The current package definition needs bootstrap binaries, which currently
are only defined for x86_64-linux and i686-linux, so --system=aarch64-linux
cannot work.
Doing --target=aarch64-linux-gnu should work though (untested).
> but it fails on the following line:
>
> \ 'configure-bin' phasebuilder for `/gnu/store/b6j0zdnbpdhx81npbk25m4nls5y1h3f5-ghc-7.10.2.drv' failed with exit code 1
>
> I have attached the log for the failed ghc build. The first error there seems to be:
>
> /tmp/guix-build-ghc-7.10.2.drv-0/ghc-7.10.2/ghc-bin/ghc-7.8.4/utils/ghc-pwd/dist-install/build/tmp/ghc-pwd: cannot execute binary file: Exec format error
>
> Seeing as this works fine for x86, I'm guessing that a ghc-pwd is being used that was compiled for x86, maybe an error in setting up cross compiling?
>
> Thanks,
> Zacchae
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-10-01 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 22:28 bug#50858: Installing git-annex for aarch64 fails on ghc build Zacchaeus Scheffer
2021-10-01 20:16 ` Maxime Devos [this message]
2021-10-03 12:32 ` Efraim Flashner
2023-11-24 14:56 ` Simon Tournier
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=ccb0664d76de0e2cb0184dce5a633e917f6fb380.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=50858@debbugs.gnu.org \
--cc=zaccysc@gmail.com \
/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).