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
Ludovic Courtès writes:
>> I wonder if some errors could be caught at build time, before attempting
>> to start the service.
>>
>> If in the derivation to build the configuration file, nginx is run
>> against the built config file with -t, that might spot errors at
>> derivation build time.
>
>
Hi Gábor,
Gábor Boskovits skribis:
> I would like to add some more information to this, which I encountered when
> trying to find a solution to the last-modified issue:
>
> 1. the nginx configuration can only be extended using server blocks, so it
> is not possible to inject a location or a
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
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
‐‐‐ 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
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
Hi,
Christopher Baines skribis:
> Ludovic Courtès writes:
>
>> It’s nice that we have but I noticed that, unlike
>> most or all other configuration records that we have, it’s possible to
>> create an record that leads to a syntactically
>> invalid nginx config file.
>>
>> For example, if you
On Wed, 2019-09-11 at 21:48 +0200, Ricardo Wurmus wrote:
> Hi Jesse,
>
> > I have been trying to set up ardour, but jackd doesn't start in
> > real-
> > time mode. I made an os definition that replicates this issue when
> > I
> > use a VM[0].
> > [0]
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
Hello,
Jan Nieuwenhuizen writes:
> Are you using the core-updates-next branch?
No, how do I do that?
Best regards,
Vivien
Ludovic Courtès writes:
> It’s nice that we have but I noticed that, unlike
> most or all other configuration records that we have, it’s possible to
> create an record that leads to a syntactically
> invalid nginx config file.
>
> For example, if you have a location block like this:
>
>
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
13 matches
Mail list logo
