Installing git-annex for aarch64 fails on ghc build

  • Open
  • quality assurance status badge
Details
4 participants
  • Efraim Flashner
  • Maxime Devos
  • Zacchaeus Scheffer
  • Simon Tournier
Owner
unassigned
Submitted by
Zacchaeus Scheffer
Severity
wishlist
Z
Z
Zacchaeus Scheffer wrote on 28 Sep 2021 00:28
(address . bug-guix@gnu.org)
CAJejy7=fnxBTUfP3YfHyeR6=wOFJ-rCHFnspP6rD+zz2R_G7Hw@mail.gmail.com
Hi Guix!

I'm trying to install git-annex for aarch64, 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: file
M
M
Maxime Devos wrote on 1 Oct 2021 22:16
ccb0664d76de0e2cb0184dce5a633e917f6fb380.camel@telenet.be
Zacchaeus Scheffer schreef op ma 27-09-2021 om 18:28 [-0400]:
Toggle quote (4 lines)
> 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).

Toggle quote (12 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iI0EABYKADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYVdsuxccbWF4aW1lZGV2
b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7sd6AQDXWZyMOJQfXaMrCyW8/el824B/
t/VT/oFMGPN9YkEoIgEA6K+OFbf463ide63gmJ9ho1yaqOy0vDa/qT66IhFvkwk=
=bsjs
-----END PGP SIGNATURE-----


E
E
Efraim Flashner wrote on 3 Oct 2021 14:32
(name . Maxime Devos)(address . maximedevos@telenet.be)
YVmixXJ5jII19BIj@3900XT
On Fri, Oct 01, 2021 at 10:16:59PM +0200, Maxime Devos wrote:
Toggle quote (12 lines)
> 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).

(ins)efraim@3900XT ~/workspace/guix$ time torsocks ./pre-inst-env guix build --no-grafts git-annex --target=aarch64-linux-gnu
guix build: error: gnu/packages/haskell-apps.scm:345:2: git-annex@8.20210903: build system `haskell' does not support cross builds

Interestingly it might be easier to get the haskell-build-system to
support cross compiling than to find the upstream blessed binary for one
of the GHC releases and use that as a bootstrap for later GHC releases
on aarch64.

Toggle quote (16 lines)
>
> > 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



--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmFZosUACgkQQarn3Mo9
g1Fy/Q/+N6sjnpG3PhKi+K8LuAbMNyCAcEDdNtnzpPkjTLp1h2HaiNLW8umaF6Kd
w+VmTE5YWHidzsF4T1dn1H8nv8jA6072f+Er/rxjDz8uSxTmQur38nDulxwqRQuz
lCX6qUNxQIOanzGbu6d68NhAF4zoPfPLX2F6IWJL6MwC1RJ0ZoHHiQxrEUCd3Ky7
ZJ2N/C0qYY1S0+m+p+AqIhZcmH3vgUNyhuWxz+gTwH096/QLmOQj6UaiHG8VyTM6
Yv1zxRezzFVUYrlQDamqky0aKV05PdWQCmEJcv+bxBy94ADrVGuzx19IJcIuiopx
b8IUN4WijRFZ+Se49spMYPbF74TynS1v0L2ZjJOEUckVqhCvteOWoF30vW6NyY7Y
/uP5dkAmbXgMZzqsNvQ32pzPW0oIocy13K7alFh+HIswzcsd4QOvxmkNPXKuqgYO
9YyAqBGfsCEZWxpLAndHzKsWarw3+4Zu0BIMTr3EkOZ/I1oAJzLutu4rgWI467pw
+fjQI4881AEsHePReCFo0GQN/dduLR2RWpeRtQWXHNDoItNRhnHUEQmiOyACXxC6
wlMX42IENacE19WKn2Ty0P6ODK+jsM64hFyt7FDLCMGYBBTYo/CagkWwnsXiDVCf
e7e8Kgv+l+skkacIhF+4MizGHRfsigiUtW5TUN5D6xK7hoRSQQ4=
=2upo
-----END PGP SIGNATURE-----


S
S
Simon Tournier wrote on 24 Nov 2023 15:56
(name . Zacchaeus Scheffer)(address . zaccysc@gmail.com)(address . 50858@debbugs.gnu.org)
87wmu7ci9d.fsf@gmail.com
Hi,

On Mon, 27 Sep 2021 at 18:28, Zacchaeus Scheffer <zaccysc@gmail.com> wrote:

Toggle quote (4 lines)
> 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?

To my knowledge, the system aarch64 is not supported. The GHC bootstrap
is currently implemented for x86_64 and i686, only.

Moreover, the Haskell build system does not support cross-builds, again
to my knowledge.

There is no mean to compile git-annex for aarch64. Therefore, it is
expected that it fails.

Cheers,
simon
S
S
Simon Tournier wrote on 24 Nov 2023 15:56
control message for bug #50858
(address . control@debbugs.gnu.org)
87v89rci97.fsf@gmail.com
severity 50858 wishlist
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 50858@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 50858
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch