bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-15 Thread Jan Nieuwenhuizen
Vivien Kraus writes: >> Are you using the core-updates-next branch? > > No, Ah. In that case it's a `know bug' that is being worked on. > how do I do that? I looked into core-updates-next and at the moment it does not seem to be in a really usable state, in other words: work in progress.

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread Vivien Kraus
Hello, Jan Nieuwenhuizen writes: > Are you using the core-updates-next branch? No, how do I do that? Best regards, Vivien

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread Vivien Kraus
Hello, Danny Milosavljevic writes: > The purpose of "remove-extra-references" seems to be to shrink the > number of recorded dependencies, so maybe compare it with the unshrinked > list of dependencies by printing the latter out (apparently it should be > inside Config_heavy.pl and Config.pm

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread Jan Nieuwenhuizen
Vivien Kraus writes: > Trying to run 'guix build --target=x86_64-w64-mingw32 perl' results in > the following exception in the latest stages of the build: Are you using the core-updates-next branch? It has a many cross-compilation fixes, notably

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread Danny Milosavljevic
Further information: According to gnu/packages/cross-base.scm, cross-gcc contains either "libc" or "mingw-source" in the mingw case--I don't know why, but that's what it says. The purpose of "remove-extra-references" seems to be to shrink the number of recorded dependencies, so maybe compare it

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread Danny Milosavljevic
Looking at the source code of phase "remove-extra-references" and assuming that the "out" output exists, probably the "libc" input doesn't exist. set-cross-path/mingw guards against this case, so apparently it is normal that "libc" input can be missing and perl should be guarding against it, but

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread Vivien Kraus
P writes: > Seems like cross compiling with mingw is broken for other packages too, I > tried the guile example about a week ago and also Lua (which is a super > portable language, so it should work everywhere, usually without > modifications) and neither worked. Oops. I was hoping I could

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread P via Bug reports for GNU Guix
‐‐‐ Original Message ‐‐‐ On Saturday, September 14, 2019 7:53 AM, Vivien Kraus wrote: > Hello guix, > > Trying to run 'guix build --target=x86_64-w64-mingw32 perl' results in > the following exception in the latest stages of the build: > > phase `install' succeeded after 36.7 seconds

bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'

2019-09-14 Thread Vivien Kraus
Hello guix, Trying to run 'guix build --target=x86_64-w64-mingw32 perl' results in the following exception in the latest stages of the build: phase `install' succeeded after 36.7 seconds starting phase `remove-extra-references' Backtrace: 13 (primitive-load