I think this issue was wrongly retitled. While the
webkitgtk-with-libsoup2 *was* also an issue (now fixed) the
configure phase error as originally reported (reproduced below for
clarity) is still there.
CMake Error at
close 57134
quit
This is fixed with
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=fafd3caef0d51811a5da81d6061789e2908b0dac
See: https://issues.guix.gnu.org/65646
The latter is the aalib package which is for ascii art.
See https://issues.guix.gnu.org/57134 for my proposed solution.
(that is, just leaving it out)
That is not sufficient however to get freecad to build, the
original error reported above still occurs then.
This still fails for me, same error.
To be clear, substitutable means there is a binary available from
one of the substituation servers?
If so, guix is not using it as it tries to build freecad, starting
with a configure, where it then fails.
What am I missing?
I am using a manifest
Fails to build on powerpc64le with a very similar error, log
attached.
tldr: "error: ‘FFI_SYSV’ undeclared"
(I'm assuming sbcl-cffi-0.24.1 is just a newer name/version of
sbcl-cffi-libffi)
dx7fab1f6fm5w95maajxcy0r9jv3xy-sbcl-cffi-0.24.1.drv.bz2
Description: Build log of sbcli-cffi-0.24.1
During the check phase of building go-1.16.15 (as dependency of
ungoogled-chromium) a failure occurs:
https://dpaste.org/ib5CZ :
--- FAIL: TestTrivialExecutable (3.43s)
shared_test.go:484: file too large: got 202752, want <= 10
--- FAIL: TestTrivialExecutablePIE (0.61s)
[Marcel van der Boom]:
[Efraim Flashner]:
About 2 months ago I spent some time and got the rust bootstrap
working
for riscv64-linux. I would suggest looking at the staging
branch since
there the rust bootstrap version is at 1.54.
Ah, I didn't even think of that, thanks! Will try
The freecad package fails to build. The following error is the
relevant part from the log.
I'm on powerpc64le, which is usually somewhat problematic in
building. Not sure if that is relevant for this issue though.
--8<---cut here---start->8---
CMake
[Thiago Jung Bauermann]:
Is this on master, or core-updates? On master, freecad-0.20.1
builds
fine on x86_64-linux, but on powerpc64le-linux it doesn't get
built
because of a dependency failure:
I get the same build failure in 'hdf4-alt' as you posted
above. This is in the check phase on
I use a Talos II machine as my daily driver and slowly migrating
as many packages to GUIX along the way. The kernel I am running
comes fromm https://archlinuxpower.org/
For many packages, rust is getting to be the bottleneck as a
dependency that does not build.
From what I can see
[Efraim Flashner]:
Is anyone familiar with this working on rust on powerpc64 for
the
powerpc64le-linux system?
About 2 months ago I spent some time and got the rust bootstrap
working
for riscv64-linux. I would suggest looking at the staging branch
since
there the rust bootstrap version
For reference: this is the mrustc bug that needs resolving
https://github.com/thepowersgang/mrustc/issues/194
Building gst-plugins-good on powerpc64le (Talos II machine)
produces a link error related to aalib.
Commenting out the 'aalib' input makes the build succeed.
Relevant snippet from the build log below.
--8<---cut here---start->8---
[444/851] Linking
I see that the full build log expired on the paste site.
Is any additional info needed here, other than the excerpt of the
log?
I suspect the check error is a safety precaution to ensure
executables are of reasonable size, but reasonable is perhaps a
bit different on the POWER9 platform?
[Efraim Flashner]:
I'm currently working on bootstrapping go-1.17.11 directly from
gccgo,
so we'd be able to skip 1.16 entirely. Currently it works on
x86_64-linux but not on riscv64-linux. If you want to test
something
like that on powerpc64le that'd be great.
Sure, can you point me in
[Efraim Flashner]:
[...]
just removing the native-inputs field completely from 1.17
should try to
make go-1.17 build with gccgo. Then try to build go@1.17.
That does indeed start a gccgo build and fails after a while with
this:
( https://dpaste.org/3UwS2 has more details)
starting
* gstreamer.scm (gst-plugins-good):
skip aalib input on ppc64le
Linker errors out for unknown reasons. The ascii art is imho not important
enough to skip the whole package from being included for ppc64le.
---
gnu/packages/gstreamer.scm | 75 --
This has been resolved with the 1.22.2 update.
close
quit
reopen 57134
quit
Apologies for the noise. I had a manifest in place working around
the bug, but unfortunately the bug is still there.
Looking at
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=024a8b39957203f3a3cb93c87746c35635b81e57
it might make sense to do the same for the 'powerpc64le' target as
well?
iled to compute the derivation for Guix (version:
"aa9ac252206615713ab988d7068da9e14a9bccc0"; system:
"powerpc64le-linux";
host version: "e5c130c0f90a7dacc8d223eee494a1b1105dd94a";
pull-version: 1).
--
Marcel van der Boom → mar...@van-der-boom.nl
21 matches
Mail list logo
