As a GUIX aarch64 user on many devices, I can say it’s not a common problem.
How much RAM do you have on your device? Do you have swap/zram?
It seems to be still there, even after dfda2cc5f6a57a0b89b98f389a2f28bf1e94eaa4
I just checked, this one is still relevant as of
b21d05d232ec0aba5abec20e83cc52c1d5163cc3
test@guix_test ~/guix$ ./pre-inst-env guix refresh -u feathernotes
gnu/packages/task-management.scm:293:13: feathernotes: updating from version
0.10.0 to version 1.0.0...
guix refresh: error: mkstemp: Read-only file system
Guix system is at b21d05d232ec0aba5abec20e83cc52c1d5163cc3
This one is done with https://issues.guix.gnu.org/55806. I suggest closing it
as resolved.
This one is done with https://issues.guix.gnu.org/55806. I suggest closing it
as resolved.
Another reproducer:
guix build librem-ec-acpi-linux-module --target=aarch64-linux-gnu
Fails with the same error. It doesn’t require external packages like the
previous reproducer.
I don’t know the reason it happens. Maybe it’s somehow related to file-append
hack that is used to set driver location in the repo. The other problem can be
about
inputs or native-inputs being empty. Anyway, package definition looks fine to
me and I suppose there’s a problem with set-paths phas
Reproducer:
guix system image -t iso9660 gnu/system/install.scm
This command fails on aarch64 host. It doesn’t if I manually remove
uvesafb-service-type from the list. It is impossible(and not needed) to run
uvesafb on non-x86 machines at the moment, so I think it should be included
only in x86_
Related?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100341
Ok, I tried to format them :)
0001-Image-API-support-VFAT-partitions-in-MBR.patch
Description: Binary data
0002-Image-API-support-VFAT-partitions-in-GPT.patch
Description: Binary data
0003-Image-API-support-boot-flag.patch
Description: Binary data
0004-Update-copyright.patch
Description: Bi
I can build it natively on aarch64 or x86_64. Only cross-compilation fails
To reproduce, run (on x86_64 host)
guix build btrfs-progs --target=aarch64-linux-gnu
Output:
configure: error: Package requirements (libudev) were not met:
No package 'libudev' found
Consider adjusting the PKG_CONFIG_PATH
Here’s the last patch in the set that adds support for the boot flag. It should
be merged after mbr-support-vfat-partitions.patch and
gpt-support-vfat-partitions.patch
The issue can be closed as soon as all three patches are merged.
Have a nice day!
support-bootable-partitions.patch
Descriptio
This patch fixes GPT support for fat partitions. Should be applied after
gpt-support-vfat-partitions.patch
gpt-support-vfat-partitions.patch
Description: Binary data
I have written a small patch to partially fix the issue. Flags are still not
set. GPT is still not fixed. There’s no need to return file systems that are
not supported in make-partition-image function in gnu/build/image.scm
mbr-support-vfat-partitions.patch
Description: Binary data
Comand
guix build u-boot-pinebook
--with-git-url=u-boot-pinebook=https://github.com/u-boot/u-boot
fails with tools/image-host.c:17:10: fatal error: openssl/pem.h: No such file
or directory
I tested it on both x86_64 and aarch64 hosts.
merge 55500 54370
> 18 мая 2022 г., в 17:19, Zomb Hacker написал(а):
>
> Greetings.
> Website of the GNU Guix project is not available from Russia.
> Is this a conscious decision based on the recent events, or the problem is
> not on your side?
> Best regards,
> Yaryshev Alexey
Issue’s not there!
My fault I didn’t wait til guix package is updated.
PASS: tests/guix-shell-export-manifest.sh
Thank you!
> 17 мая 2022 г., в 18:01, Pavel Shlyak написал(а):
>
> [pavel@alarm factory]$ cat /proc/cpuinfo
> processor : 0
> BogoMIPS : 48.00
> Featur
[pavel@alarm factory]$ cat /proc/cpuinfo
processor : 0
BogoMIPS: 48.00
Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp
asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm dit
uscat ilrcpc flagm sb paca pacg dcpodp flagm2 frint
CPU imp
I can recommend to configure VPN on a router as a temporary solution. You can
also clone GUIX repos on some other device (with VPN) and use it for
installation.
It looks like setting esp flag with (flags '(esp)) also sets file system to
vfat. However,
1. I still cannot resolve boot flag issue
2. I do not need that flag and I’d be glad getting correct partition without it
I found it. It blows my mind. Let me just cry out here.
(define (partition->dos-type partition)
;; Return the MBR partition type corresponding to the given PARTITION.
;; See: https://en.wikipedia.org/wiki/Partition_type.
(let ((flags (partition-flags partition)))
(con
I have a scheme code like
(define rpi-boot-partition
(partition
(size (* 128 (expt 2 20)))
(label "BOOT")
(file-system "vfat")
(flags '())
(initializer (gexp initialize-efi-partition
(define rpi-root-partition
(partition
(size 'guess)
(label "RASPIROOT")
(file-system "ext4")
(flags '(boot))
(
I have a scheme code like
(define rpi-boot-partition
(partition
(size (* 128 (expt 2 20)))
(label "BOOT")
(file-system "vfat")
(flags '())
(initializer (gexp initialize-efi-partition
(define rpi-root-partition
(partition
(size 'guess)
(label "RASPIROOT")
(file-system "ext4")
(flags '(boot))
(
24 matches
Mail list logo
