Hello Guix,
I've recently noticed that cross-compiling with a different GCC was not
possible by simply adding them as native inputs the same way we can
already do when compiling natively.
Here's an example in our package collection that fails to cross-compile
for that reason:
"pelzflorian (Florian Pelz)" skribis:
> Ludovic Courtès writes:
>> So my guess is that things will be much better if we swap these two
>> lines.
>
> This was helpful, but not enough.
Sorry, I think I wasn’t thinking at full speed. There needs to be zero
daemons running while we copy the
Hi again.
Ludovic Courtès writes:
> So my guess is that things will be much better if we swap these two
> lines.
This was helpful, but not enough.
Swapping them may have improved the likelihood of being able to retry,
but the issue is still there. I uploaded as installer-dump-5f9f8dbe,
but it
Hi again,
Joseph Turner writes:
> This occurred on a guix installation on a foreign distro, yes. On a VPS I
> rent, which I recently upgraded to Debian 11. Guix was installed using `apt
> install guix`.
Didn't think bullseye would be shipping 1.2, you may have better luck
with the bookworm
Hello Josselin,
This occurred on a guix installation on a foreign distro, yes. On a VPS I rent,
which I recently upgraded to Debian 11. Guix was installed using `apt install
guix`.
Thank you!
Joseph
On December 13, 2022 2:19:06 AM PST, Josselin Poiret wrote:
>Hi,
>
>Joseph Turner via Bug
"pelzflorian (Florian Pelz)" skribis:
> (provision '(maybe-uvesafb))
> (requirement '(file-systems))
> (start #~(lambda ()
> -(or (file-exists? "/dev/fb0")
> -(invoke #+(file-append kmod "/bin/modprobe")
> -
"pelzflorian (Florian Pelz)" writes:
> I will next try using 'load-linux-modules-from-directory' and no
> modprobe.
I tried the attached patch. Doesn’t work, still black (in QEMU).
Says the dmesg:
> [ 11.183789] shepherd[1]: Service user-homes has been started.
> [ 11.184555] shepherd[1]:
"pelzflorian (Florian Pelz)" skribis:
> Ludovic Courtès writes:
>> Specifically, here’s the minimal change we should test:[…]
>> +(unless (file-exists? "/dev/fb0")
>> + (setenv "LINUX_MODULE_DIRECTORY"
>> +
Ludovic Courtès writes:
> Specifically, here’s the minimal change we should test:[…]
> +(unless (file-exists? "/dev/fb0")
> + (setenv "LINUX_MODULE_DIRECTORY"
> + "/run/booted-system/kernel/lib/modules")
Thanks for the patch.
Thank you Josselin.
Josselin Poiret writes:
> I don't think there's a race issue with the files being available:
Yes apparently, but it is some kind of race.
BTW it happens on master branch too despite its more recent linux.
> By the way, why is the modprobe binary inside a #+? The target
Hi,
Joseph Turner via Bug reports for GNU Guix writes:
> Building from this channel:
> guix https://git.savannah.gnu.org/git/guix.git e84042f
> Computing Guix derivation for 'x86_64-linux'... |guix pull: error: You found
> a bug: the program '/gnu/store/2xp4c2dsiyjpfa
>
Ludovic Courtès skribis:
> So you may need to add:
>
> (setenv "LINUX_MODULE_DIRECTORY" "/run/booted-system/kernel/lib/modules")
Specifically, here’s the minimal change we should test:
diff --git a/gnu/system/install.scm b/gnu/system/install.scm
index f6f1923121..a512ace29e 100644
---
Hi,
Pierre Langlois skribis:
> I'm not sure I follow, I'd suggest to revert the revert and then apply a
> fix in the same commit, that way it can easily be reverted again if it's
> problematic, that's probably what you meant already?
Sounds good to me. The commit log can be similar to the
Hi again,
Ludovic Courtès skribis:
> It looks like the store is in a broken state, with its database not
> matching its actual contents. The ‘install-system’ procedure is
> supposed to protect against that by making a backup of the database
> before starting the installation and restoring it
Hi,
"pelzflorian (Florian Pelz)" skribis:
> I now uploaded an installer-dump-bade9971 of me reproducing the issue.
Here’s the relevant syslog excerpt (this was with 1.4.0rc1) where we can
see the point where you unplugged the Ethernet connection:
--8<---cut
15 matches
Mail list logo
