Looks like something changed between 2.34 (on master) and 2.36 (on
core-updates) which caused ‘share/X11/rules/base’ to generate
improperly.
On core-updates:
--8<---cut here---start->8---
~/src/guix-core-updates $ ./pre-inst-env guix build
> The later, I'd say; we're all volunteers :-).
Fair enough!
The Guix version of rust-analyzer that is in rust-apps.scm is somehow
dependent on rustc 1.60.0 and seems to use it internally to do
compilation and checks.
Guix recently published rustc v1.65.0 to the repo and after pulling that
in, many compilations fail with some very strange error
Hello,
attached is a new commit in old syntax, mixing both our commits.
I have confirmed that it does not change the gcc-11 build on x86_64 and i686.
But do we need "--force" for patching?
Could you maybe check again whether this builds gcc-11 on powerpc?
If yes, we can push it, and feel free
Am Thu, Apr 13, 2023 at 02:46:00PM +0100 schrieb Christopher Baines:
> Thanks for figuring this out Andreas! I've managed to apply this change
> in the relevant place, and it appears to work.
Good news, thanks!
> + #$@(if (and (target-ppc64le?)
> + (version>=?
Andreas Enge writes:
> In the file
>libstdc++-v3/src/c++17/floating_from_chars.cc
> previous functions have code like this:
> #if _GLIBCXX_USE_CXX11_ABI
> buffer_resource mr;
> pmr::string buf();
> #else
> string buf;
> if (!reserve_string(buf))
> return make_result(first, 0,
I may as well try to provide a patch. It is untested even on x86_64,
since it requires quite a few rebuilds. If it works on powerpc, it should
probably be made conditional on the architecture to avoid a world rebuild.
I do not know whether this is possible in the patches field in an origin.
Hello,
recently I claimed that powerpc was repaired, but I must have made a mistake.
It is still completely broken:
https://ci.guix.gnu.org/eval/391720/dashboard?system=powerpc64le-linux
due to this:
https://issues.guix.gnu.org/61879
It does not look easy to fix, but might be *the*
