rust-team branch merged
I've merged the rust-team branch into master. I've dropped rust for aarch64-linux again for now until I can get it built on cuirass so it's not holding up the branch any longer. Unfortunately I forgot about the mesa update earlier so there's more rebuilds than I expected. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: rust-team branch merged
Efraim Flashner writes: > I've merged the rust-team branch into master. I've dropped rust for > aarch64-linux again for now until I can get it built on cuirass so it's > not holding up the branch any longer. Do you know if it actually doesn't build, or whether it's just a berlin/Cuirass issue? While I appreciate the waiting for the build farm to catch up, I think that in the case of aarch64-linux substitutes from ci.guix.gnu.org, whatever problems are causing the substitute availability to be so low aren't really going to be helped by waiting, something more is probably needed. signature.asc Description: PGP signature
Re: 04/09: gnu: mesa: Update to 23.0.3.
John Kehayias writes: > Hi Christopher and Maxim, > > On Mon, May 08, 2023 at 02:41 AM, Christopher Baines wrote: > >> guix-comm...@gnu.org writes: >> >>> apteryx pushed a commit to branch master >>> in repository guix. >>> >>> commit 0be7838105806819f4586ec9130382a66a22880e >>> Author: Kaelyn Takata >>> AuthorDate: Thu May 4 20:12:46 2023 + >>> >>> gnu: mesa: Update to 23.0.3. >>> >>> * gnu/packages/gl.scm (mesa): Update to 23.0.3. >>> [source]: Remove obsolete patch and update HTTPS url. >>> [arguments]: Enable the crocus gallium driver. >>> * gnu/packages/patches/mesa-fix-sporadic-test-failures.patch: Delete >>> file. >>> * gnu/local.mk (dist_patch_DATA): Remove it. >>> --- >>> gnu/local.mk | 1 - >>> gnu/packages/gl.scm| 14 --- >>> .../patches/mesa-fix-sporadic-test-failures.patch | 27 >>> -- >>> 3 files changed, 5 insertions(+), 37 deletions(-) >> >> → guix refresh -l mesa >> Building the following 1954 packages would ensure 4257 dependent >> packages are rebuilt ... >> >> >> I know there's been some discussion about changing processes regarding >> changes like this that impact lots of packages, but as far as I'm aware, >> the documented process hasn't changed yet. So should this have gone to >> core-updates, and not been directly pushed to master? >> > > I should take some responsibility over what happened here as I had > volunteered as a sort of "branch manager" (to use the terminology > later in this thread) but I was a bit slower than I wanted. My plan > was roughly in line with what we are discussing, reviewing the > patches, pushing to a new "mesa-updates" branch, and then asking for > someone to start a build job. We could then have people more easily > test or just to check build for build failures and ensure good > substitute coverage upon merging. Don't feel responsible for not doing things John, I'm advocating here for less haste and more caution. signature.asc Description: PGP signature
Re: rust-team branch merged
On Tue, May 09, 2023 at 09:33:46AM +0100, Christopher Baines wrote: > > Efraim Flashner writes: > > > I've merged the rust-team branch into master. I've dropped rust for > > aarch64-linux again for now until I can get it built on cuirass so it's > > not holding up the branch any longer. > > Do you know if it actually doesn't build, or whether it's just a > berlin/Cuirass issue? I've managed to build it myself on my own pinebook pro and used that to build librsvg and python-cryptography. riscv64-linux actually needs more work to fix so it's building again. > While I appreciate the waiting for the build farm to catch up, I think > that in the case of aarch64-linux substitutes from ci.guix.gnu.org, > whatever problems are causing the substitute availability to be so low > aren't really going to be helped by waiting, something more is probably > needed. The way its currently setup all we need to do is re-add aarch64-linux to the supported-systems of rust-bootstrap and it'll be enabled again, and build successfully eventually. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: rust-team branch merged
Hello, Am Tue, May 09, 2023 at 11:54:00AM +0300 schrieb Efraim Flashner: > The way its currently setup all we need to do is re-add aarch64-linux to > the supported-systems of rust-bootstrap and it'll be enabled again, and > build successfully eventually. I am confused by what happened; did you disable rust on aarch64 for everyone, or just building on the farm? If the first, that sounds like a pity, since at worst people can still compile packages by themselves. Andreas
Re: rust-team branch merged
PS: Congratulations for getting the first team branch through! And thanks for waiting until the core-updates merge :-)
Re: rust-team branch merged
Andreas Enge writes: > Hello, > > Am Tue, May 09, 2023 at 11:54:00AM +0300 schrieb Efraim Flashner: >> The way its currently setup all we need to do is re-add aarch64-linux to >> the supported-systems of rust-bootstrap and it'll be enabled again, and >> build successfully eventually. > > I am confused by what happened; did you disable rust on aarch64 for everyone, > or just building on the farm? If the first, that sounds like a pity, since > at worst people can still compile packages by themselves. Yeah, while I appreciate paying attention to what substitutes are available, I think we should add aarch64-linux back to the supported systems, regardless of what ci.guix.gnu.org is doing. signature.asc Description: PGP signature
RISC-V (riscv64-linux) substitutes are coming
Hey! Almost a year ago now [1] I mentioned that I had received a HiFive Unmatched board, but I hadn't got it doing anything yet. 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html In the last few days I've made some time to take a look at it again and try to get it connected up to the bordeaux build farm. This has been somewhat successful, you should be able to see the machine (named rochor) on the prototype activity viewer [2]. 2: https://bordeaux.guix.gnu.org/activity Unfortunately it seems a bit stuck trying to upload the build results back to the coordinator due to the suspendable ports issues in guile-gnutls, but that should be fixed in the latest release so hopefully I'll be able to deploy that fix soon. It's also just currently a bare board hooked up to a spare power supply I have. I'll try and cost up a dedicated power supply plus case for it, and if anyone has suggestions for minimal mini-itx compatible cases, please let me know! This is a start, but more hardware will be needed to keep up with the master branch, plus testing patches and other branches, so if you have hardware to hand, or know of hardware available for purchase that might be suitable, that would be really useful to know about. Thanks, Chris signature.asc Description: PGP signature
Re: rust-team branch merged
On Tue, May 09, 2023 at 02:22:36PM +0100, Christopher Baines wrote: > > Andreas Enge writes: > > > Hello, > > > > Am Tue, May 09, 2023 at 11:54:00AM +0300 schrieb Efraim Flashner: > >> The way its currently setup all we need to do is re-add aarch64-linux to > >> the supported-systems of rust-bootstrap and it'll be enabled again, and > >> build successfully eventually. > > > > I am confused by what happened; did you disable rust on aarch64 for > > everyone, > > or just building on the farm? If the first, that sounds like a pity, since > > at worst people can still compile packages by themselves. > > Yeah, while I appreciate paying attention to what substitutes are > available, I think we should add aarch64-linux back to the supported > systems, regardless of what ci.guix.gnu.org is doing. Thank you all for the encouragement and feedback. I've re-enabled aarch64 for rust. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: RISC-V (riscv64-linux) substitutes are coming
On Tue, May 09, 2023 at 02:40:21PM +0100, Christopher Baines wrote: > Hey! > > Almost a year ago now [1] I mentioned that I had received a HiFive > Unmatched board, but I hadn't got it doing anything yet. > > 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html Some would say that's almost two years ago! > In the last few days I've made some time to take a look at it again and > try to get it connected up to the bordeaux build farm. > > This has been somewhat successful, you should be able to see the machine > (named rochor) on the prototype activity viewer [2]. > > 2: https://bordeaux.guix.gnu.org/activity > > Unfortunately it seems a bit stuck trying to upload the build results > back to the coordinator due to the suspendable ports issues in > guile-gnutls, but that should be fixed in the latest release so > hopefully I'll be able to deploy that fix soon. > > It's also just currently a bare board hooked up to a spare power supply > I have. I'll try and cost up a dedicated power supply plus case for it, > and if anyone has suggestions for minimal mini-itx compatible cases, > please let me know! > > This is a start, but more hardware will be needed to keep up with the > master branch, plus testing patches and other branches, so if you have > hardware to hand, or know of hardware available for purchase that might > be suitable, that would be really useful to know about. That's really exciting! I've been having good luck with the visionfive1 as a build machine. My visionfive2 gets a little hot and I'm looking at getting a desk fan to blow at it and some of the other boards that get a bit hot while building. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: RISC-V (riscv64-linux) substitutes are coming
Christopher Baines writes: > This is a start, but more hardware will be needed to keep up with the > master branch, plus testing patches and other branches, so if you have > hardware to hand, or know of hardware available for purchase that might > be suitable, that would be really useful to know about. Hello I have a visionfive2 4GiB memory model with a nvme disk, does it suitable to join the guix build farm? My home network is behind NAT. Thank you!
Re: RISC-V (riscv64-linux) substitutes are coming
Efraim Flashner writes: > [[PGP Signed Part:Undecided]] > On Tue, May 09, 2023 at 02:40:21PM +0100, Christopher Baines wrote: >> Hey! >> >> Almost a year ago now [1] I mentioned that I had received a HiFive >> Unmatched board, but I hadn't got it doing anything yet. >> >> 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html > > Some would say that's almost two years ago! Indeed, I got my maths wrong! Time is really getting on :/ >> In the last few days I've made some time to take a look at it again and >> try to get it connected up to the bordeaux build farm. >> >> This has been somewhat successful, you should be able to see the machine >> (named rochor) on the prototype activity viewer [2]. >> >> 2: https://bordeaux.guix.gnu.org/activity >> >> Unfortunately it seems a bit stuck trying to upload the build results >> back to the coordinator due to the suspendable ports issues in >> guile-gnutls, but that should be fixed in the latest release so >> hopefully I'll be able to deploy that fix soon. >> >> It's also just currently a bare board hooked up to a spare power supply >> I have. I'll try and cost up a dedicated power supply plus case for it, >> and if anyone has suggestions for minimal mini-itx compatible cases, >> please let me know! >> >> This is a start, but more hardware will be needed to keep up with the >> master branch, plus testing patches and other branches, so if you have >> hardware to hand, or know of hardware available for purchase that might >> be suitable, that would be really useful to know about. > > That's really exciting! > > I've been having good luck with the visionfive1 as a build machine. My > visionfive2 gets a little hot and I'm looking at getting a desk fan to > blow at it and some of the other boards that get a bit hot while > building. Cool, well let me know if any of those can be hooked up to the build farm. It's quite easy and obviously you can still use them (and just stop the build coordinator agent) if you need to. signature.asc Description: PGP signature
Re: RISC-V (riscv64-linux) substitutes are coming
Hi, On Tue, May 9, 2023 at 6:51 AM Christopher Baines wrote: > > Unfortunately it seems a bit stuck trying to upload the build results > back to the coordinator due to the suspendable ports issues in > guile-gnutls While I'm totally unfamiliar with the build farm, I thought I'd give a quick shoutout to ZeroMQ. [1] I had great success with it in similar settings. "Sometimes you just need a better socket" was the motto of the lead developer and advocate Pieter Hintjens, who unfortunately left too soon. ZeroMQ performs well when compared with other messaging systems. [2][3][4] Kind regards Felix [1] https://zeromq.org/ [2] https://indico.cern.ch/event/354137/contributions/1763290/subcontributions/153483/attachments/701686/963362/ZeroMQ-tCSC-Aram.pdf [3] https://www-acc.gsi.de/wiki/pub/Frontend/MeetingCMW130425/CHEP-2012-NewCERNcontrolsMiddleware.pdf [4] https://accelconf.web.cern.ch/icalepcs2017/papers/mobpl05.pdf
Re: RISC-V (riscv64-linux) substitutes are coming
宋文武 writes: > Christopher Baines writes: > >> This is a start, but more hardware will be needed to keep up with the >> master branch, plus testing patches and other branches, so if you have >> hardware to hand, or know of hardware available for purchase that might >> be suitable, that would be really useful to know about. > > Hello I have a visionfive2 4GiB memory model with a nvme disk, does it > suitable to join the guix build farm? My home network is behind NAT. Yes! At least in my opinion. Ideally the build machines would be owned by guix-europe, but that's something to look at sorting out once it's up and running. The NAT is no problem, the build coordinator (intentionally) has very few requirements. The first hurdle to overcome is just getting the build coordinator agent available on the system. For the board I have, I cross compiled the guix-build-coordinator-agent-only package, then used guix archive to copy it and all the dependencies across but any approach that works is fine. Once you've got that far, let me know and I can privately send you the arguments to use when running the agent. Thanks! Chris signature.asc Description: PGP signature
Re: RISC-V (riscv64-linux) substitutes are coming
Felix Lechner writes: > Hi, > > On Tue, May 9, 2023 at 6:51 AM Christopher Baines wrote: >> >> Unfortunately it seems a bit stuck trying to upload the build results >> back to the coordinator due to the suspendable ports issues in >> guile-gnutls > > While I'm totally unfamiliar with the build farm, I thought I'd give a > quick shoutout to ZeroMQ. [1] I had great success with it in similar > settings. > > "Sometimes you just need a better socket" was the motto of the lead > developer and advocate Pieter Hintjens, who unfortunately left too > soon. ZeroMQ performs well when compared with other messaging systems. > [2][3][4] Thanks for the suggestion Felix. Generally though, I'm trying to avoid any dependencies for the build coordinator agent, since that should help to avoid problems with portability. Ideally it wouldn't have any dependencies other than the guix package itself (and the things it requires). This issue should be fixed in the latest release, and I've been running that on one of the build machines and it's been working great, so I'm quite excited :) Thanks again, Chris signature.asc Description: PGP signature
Guix CI "No space left on device"
icedtea-3.19.0 fails to build with ...
http://ci.guix.gnu.org/build/1331007/details
--8<---cut here---start->8---
repacking
/gnu/store/cyxfl45c31dg84spwkazadnmn2c94rak-icedtea-3.19.0-jdk/lib/jconsole.jar
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at sun.tools.jar.Main.copy(Main.java:823)
at sun.tools.jar.Main.copy(Main.java:854)
at sun.tools.jar.Main.extractFile(Main.java:1012)
at sun.tools.jar.Main.extract(Main.java:924)
at sun.tools.jar.Main.run(Main.java:264)
at sun.tools.jar.Main.main(Main.java:1231)
error: in phase 'strip-jar-timestamps': uncaught exception:
%exception #<&invoke-error program: "jar" arguments: ("xf"
"/gnu/store/cyxfl45c31dg84spwkazadnmn2c94rak-icedtea-3.19.0-jdk/lib/jconsole.jar")
exit-status: 1 term-signal: #f stop-signal: #f>
phase `strip-jar-timestamps' failed after 18.7 seconds
command "jar" "xf"
"/gnu/store/cyxfl45c31dg84spwkazadnmn2c94rak-icedtea-3.19.0-jdk/lib/jconsole.jar"
failed with status 1
note: build failure may have been caused by lack of free disk space
builder for `/gnu/store/x4d9c7crnzn17pw8ahxjl5jc6jjdbyn4-icedtea-3.19.0.drv'
failed with exit code 1
@ build-failed /gnu/store/x4d9c7crnzn17pw8ahxjl5jc6jjdbyn4-icedtea-3.19.0.drv
- 1 builder for
`/gnu/store/x4d9c7crnzn17pw8ahxjl5jc6jjdbyn4-icedtea-3.19.0.drv'
failed with exit code 1
--8<---cut here---end--->8---
Re: Mesa vulkan layer path fix for core-updates
Hi, --- Original Message --- On Tuesday, May 9th, 2023 at 4:51 AM, John Kehayias wrote: > > Hello, > > On Tue, Apr 25, 2023 at 04:40 PM, Kaelyn wrote: > > > Hi, > > > > --- Original Message --- > > On Tuesday, April 25th, 2023 at 2:15 PM, Andreas Enge andr...@enge.fr wrote: > > > > > Hello Kaelyn, > > > > > > thanks for your research! > > > > You're welcome! :) > > > > > Am Wed, Apr 19, 2023 at 04:07:51PM + schrieb Kaelyn: > > > > > > > * https://issues.guix.gnu.org/62176 can be closed when > > > > core-updates is merged, since core-updates contains mesa 22.2.4 > > > > * Though not exactly mesa-related, > > > > https://issues.guix.gnu.org/61364 can possibly be closed now, and > > > > almost certainly once the core-updates merge is completed. (The > > > > ticket is a number of workarounds the user applied in early Feb to > > > > be able to build their system profile using core-updates, to pick > > > > up Mesa 22 for newer hardware support. I'm not sure if any of the > > > > patches are still relevant.) > > > > > > I just closed these two. > > > > > > > * https://issues.guix.gnu.org/58887 looks like an alternate way of > > > > solving the layer path issues that > > > > https://issues.guix.gnu.org/59453 also addresses. Additionally, it > > > > adds two new nonstandard VK_*_PATH variables to vulkan-loader, > > > > with at least VK_ILAYER_PATH seeming very similar in functionality > > > > to VK_LAYER_PATH and VK_ADD_LAYER_PATH described at > > > > https://github.com/KhronosGroup/Vulkan-Loader/blob/main/docs/LoaderInterfaceArchitecture.md > > > > * https://issues.guix.gnu.org/58251 would be fixed by > > > > https://issues.guix.gnu.org/59453 > > > > I feel these two can be closed once 59453 lands, as then the manifests > > will have the store path to their corresponding shared objects. I also > > think having the full paths in the manifests will lead to fewer > > cross-version/cross-package mixing of objects, compared to setting and > > using environment variables of directories to search. > > > I haven't looked at the details, but I'm guessing these can all be > closed now? Yes they can be. As a quick smoke test, prior to these patches landing, "vulkaninfo > /dev/null" would consistently print out vulkan loader errors about not being able to open libVkLayer_MESA_device_select.so. (I call it a smoke test because that layer not being found isn't fatal; I first encountered the errors in a breaking way when packaging vulkan-validationlayers for use with the tutorial at https://vulkan-tutorial.com/.) Slightly off-topic speaking of mesa bugs: another one that can be closed is https://issues.guix.gnu.org/43849 as the issue with mesa's reproducibility was fixed with a patch that landed in meson 0.59.0 (which Guix picked up in commit b15c3dd9b0 from July 2021). > > > > > * https://issues.guix.gnu.org/62313 might need a modification to > > > > mesa e.g. to add VDPAU_DRIVER_PATH as a native-search-path (one > > > > possible solution; in my home profile I made VDPAU work by setting > > > > "VDPAU_DRIVER_PATH=/run/current-system/profile/lib/vdpau"). > > > > * https://issues.guix.gnu.org/48868 appears to be the same > > > > VDPAU_DRIVER_PATH issue as https://issues.guix.gnu.org/62313. > > > > For the VDPAU drivers, I plan to do a little more digging and some > > experimenting but I suspect defining VDPAU_DRIVER_PATH as a > > native-search-path is the best way forward. I'll send a patch once > > I've tested a change locally without having my profile set > > VDPAU_DRIVER_PATH to /run/current-system/profile/lib/vdpau. > > > I checked that both 48868 and 62313 were fixed in the recent updates > and closed both. > > Thanks for the patches! > John You're welcome! And thank you for checking and resolving the bug reports! Cheers, Kaelyn
Re: RISC-V (riscv64-linux) substitutes are coming
Christopher Baines writes: Hi Chris, > Almost a year ago now [1] I mentioned that I had received a HiFive > Unmatched board, but I hadn't got it doing anything yet. > > 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html > > In the last few days I've made some time to take a look at it again and > try to get it connected up to the bordeaux build farm. > > This has been somewhat successful, you should be able to see the machine > (named rochor) on the prototype activity viewer [2]. That's lovely! Because of my the Mes release that should have initial RISC-V support I've been looking for RISC-V substitutes. The good folks over at #bootstrappable advised me to just build using QEMU, the consensus was that gave dependable results However, I found that many packages have failing tests, mostly related to stack (overflow) checks. I looked at wip-riscv but that seems to be 1.5y old...so I've building and disabling tests over at https://gitlab.com/janneke/guix/-/tree/wip-riscv Hopefully all this isn't necessary when using real RISC-V hardware! Greetings, Janneke -- Janneke Nieuwenhuizen | GNU LilyPond https://LilyPond.org Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
Substitute not downloading
I have an up-to-date Guix but am unable to fetch the substitute from http://ci.guix.gnu.org/build/1332269/details Are substitutes only available after the evaluation has completed? --8<---cut here---start->8--- $ guix describe Generation 9May 09 2023 15:18:11(current) guix c1ffe2f repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: c1ffe2f21bd1b9ba6bd527bbabe130144a69af71 guix install ungoogled-chromium The following package will be installed: ungoogled-chromium 112.0.5615.165-1 The following derivations will be built: /gnu/store/lxix0vxmgdvvddk6wl2fdag7vrqhklky-profile.drv /gnu/store/92l92ljnq20q09bvjxlw42n5gl8shf38-ungoogled-chromium-112.0.5615.165-1.drv 611.0 MB will be downloaded chromium-112.0.5615.165.tar.xz 583.6MiB --8<---cut here---end--->8---
Re: RISC-V (riscv64-linux) substitutes are coming
Aleksandr Vityazev writes: >>> I've been having good luck with the visionfive1 as a build machine. My >>> visionfive2 gets a little hot and I'm looking at getting a desk fan to >>> blow at it and some of the other boards that get a bit hot while >>> building. > > I also use visionfive2 as my build machine. Quite happy with it. I have > a fairly large heatsink installed without a fan, the temperature does > not exceed 60 degrees at full load. > >> Cool, well let me know if any of those can be hooked up to the build >> farm. It's quite easy and obviously you can still use them (and just >> stop the build coordinator agent) if you need to. >> > > I'd give it a try. Although now there is only a 256GB ssd plugged in and > no dedicated ip address. I don't know how the coordinator works, maybe > it doesn't matter, I need to see how it all works. Cool :) 256GB is enough storage space, and there's no requirement for a dedicated IP address. signature.asc Description: PGP signature
Re: RISC-V (riscv64-linux) substitutes are coming
On Tue, May 09, 2023 at 06:24:11PM +0300, Aleksandr Vityazev wrote: > Hi, > > On 2023-05-09, 15:22 +0100, Christopher Baines wrote: > > > Efraim Flashner writes: > > > >> [[PGP Signed Part:Undecided]] > >> On Tue, May 09, 2023 at 02:40:21PM +0100, Christopher Baines wrote: > >>> Hey! > >>> > >>> Almost a year ago now [1] I mentioned that I had received a HiFive > >>> Unmatched board, but I hadn't got it doing anything yet. > >>> > >>> 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html > >> > >> Some would say that's almost two years ago! > > > > Indeed, I got my maths wrong! Time is really getting on :/ > > > >>> In the last few days I've made some time to take a look at it again and > >>> try to get it connected up to the bordeaux build farm. > >>> > >>> This has been somewhat successful, you should be able to see the machine > >>> (named rochor) on the prototype activity viewer [2]. > >>> > >>> 2: https://bordeaux.guix.gnu.org/activity > >>> > >>> Unfortunately it seems a bit stuck trying to upload the build results > >>> back to the coordinator due to the suspendable ports issues in > >>> guile-gnutls, but that should be fixed in the latest release so > >>> hopefully I'll be able to deploy that fix soon. > >>> > >>> It's also just currently a bare board hooked up to a spare power supply > >>> I have. I'll try and cost up a dedicated power supply plus case for it, > >>> and if anyone has suggestions for minimal mini-itx compatible cases, > >>> please let me know! > >>> > >>> This is a start, but more hardware will be needed to keep up with the > >>> master branch, plus testing patches and other branches, so if you have > >>> hardware to hand, or know of hardware available for purchase that might > >>> be suitable, that would be really useful to know about. > >> > >> That's really exciting! > >> > >> I've been having good luck with the visionfive1 as a build machine. My > >> visionfive2 gets a little hot and I'm looking at getting a desk fan to > >> blow at it and some of the other boards that get a bit hot while > >> building. > > I also use visionfive2 as my build machine. Quite happy with it. I have > a fairly large heatsink installed without a fan, the temperature does > not exceed 60 degrees at full load. Where did you get the heatsink from? Something generic or from the makers of the visionfive2? > > Cool, well let me know if any of those can be hooked up to the build > > farm. It's quite easy and obviously you can still use them (and just > > stop the build coordinator agent) if you need to. > > > > I'd give it a try. Although now there is only a 256GB ssd plugged in and > no dedicated ip address. I don't know how the coordinator works, maybe > it doesn't matter, I need to see how it all works. > > -- > Best regards, > Aleksandr Vityazev -- Efraim Flashner פלשנר אפרים GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: bug#63267: gcc-toolchain is missing libstdc++.so
Hi, I am proposing patch#63393 [1] which adds the output lib to gcc-toolchain. Well, quoting the comment: ;; The main raison d'être of this "meta-package" is (1) to conveniently ;; install everything that we need, and (2) to make sure ld-wrapper comes ;; before Binutils' ld in the user's profile. I think, this package gcc-toolchain should be the visible package and battery included. WDYT? 1: https://issues.guix.gnu.org/issue/63393 Cheers, simon
Re: RISC-V (riscv64-linux) substitutes are coming
On 2023-05-09, 18:57 +0300, Efraim Flashner wrote: > On Tue, May 09, 2023 at 06:24:11PM +0300, Aleksandr Vityazev wrote: >> Hi, >> >> On 2023-05-09, 15:22 +0100, Christopher Baines wrote: >> >> > Efraim Flashner writes: >> > >> >> [[PGP Signed Part:Undecided]] >> >> On Tue, May 09, 2023 at 02:40:21PM +0100, Christopher Baines wrote: >> >>> Hey! >> >>> >> >>> Almost a year ago now [1] I mentioned that I had received a HiFive >> >>> Unmatched board, but I hadn't got it doing anything yet. >> >>> >> >>> 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html >> >> >> >> Some would say that's almost two years ago! >> > >> > Indeed, I got my maths wrong! Time is really getting on :/ >> > >> >>> In the last few days I've made some time to take a look at it again and >> >>> try to get it connected up to the bordeaux build farm. >> >>> >> >>> This has been somewhat successful, you should be able to see the machine >> >>> (named rochor) on the prototype activity viewer [2]. >> >>> >> >>> 2: https://bordeaux.guix.gnu.org/activity >> >>> >> >>> Unfortunately it seems a bit stuck trying to upload the build results >> >>> back to the coordinator due to the suspendable ports issues in >> >>> guile-gnutls, but that should be fixed in the latest release so >> >>> hopefully I'll be able to deploy that fix soon. >> >>> >> >>> It's also just currently a bare board hooked up to a spare power supply >> >>> I have. I'll try and cost up a dedicated power supply plus case for it, >> >>> and if anyone has suggestions for minimal mini-itx compatible cases, >> >>> please let me know! >> >>> >> >>> This is a start, but more hardware will be needed to keep up with the >> >>> master branch, plus testing patches and other branches, so if you have >> >>> hardware to hand, or know of hardware available for purchase that might >> >>> be suitable, that would be really useful to know about. >> >> >> >> That's really exciting! >> >> >> >> I've been having good luck with the visionfive1 as a build machine. My >> >> visionfive2 gets a little hot and I'm looking at getting a desk fan to >> >> blow at it and some of the other boards that get a bit hot while >> >> building. >> >> I also use visionfive2 as my build machine. Quite happy with it. I have >> a fairly large heatsink installed without a fan, the temperature does >> not exceed 60 degrees at full load. > > Where did you get the heatsink from? Something generic or from the > makers of the visionfive2? > I bought a generic one at the marketplace. >> > Cool, well let me know if any of those can be hooked up to the build >> > farm. It's quite easy and obviously you can still use them (and just >> > stop the build coordinator agent) if you need to. >> > >> >> I'd give it a try. Although now there is only a 256GB ssd plugged in and >> no dedicated ip address. I don't know how the coordinator works, maybe >> it doesn't matter, I need to see how it all works. -- Best regards, Aleksandr Vityazev
Re: RISC-V (riscv64-linux) substitutes are coming
Hi, On 2023-05-09, 15:22 +0100, Christopher Baines wrote: > Efraim Flashner writes: > >> [[PGP Signed Part:Undecided]] >> On Tue, May 09, 2023 at 02:40:21PM +0100, Christopher Baines wrote: >>> Hey! >>> >>> Almost a year ago now [1] I mentioned that I had received a HiFive >>> Unmatched board, but I hadn't got it doing anything yet. >>> >>> 1: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00104.html >> >> Some would say that's almost two years ago! > > Indeed, I got my maths wrong! Time is really getting on :/ > >>> In the last few days I've made some time to take a look at it again and >>> try to get it connected up to the bordeaux build farm. >>> >>> This has been somewhat successful, you should be able to see the machine >>> (named rochor) on the prototype activity viewer [2]. >>> >>> 2: https://bordeaux.guix.gnu.org/activity >>> >>> Unfortunately it seems a bit stuck trying to upload the build results >>> back to the coordinator due to the suspendable ports issues in >>> guile-gnutls, but that should be fixed in the latest release so >>> hopefully I'll be able to deploy that fix soon. >>> >>> It's also just currently a bare board hooked up to a spare power supply >>> I have. I'll try and cost up a dedicated power supply plus case for it, >>> and if anyone has suggestions for minimal mini-itx compatible cases, >>> please let me know! >>> >>> This is a start, but more hardware will be needed to keep up with the >>> master branch, plus testing patches and other branches, so if you have >>> hardware to hand, or know of hardware available for purchase that might >>> be suitable, that would be really useful to know about. >> >> That's really exciting! >> >> I've been having good luck with the visionfive1 as a build machine. My >> visionfive2 gets a little hot and I'm looking at getting a desk fan to >> blow at it and some of the other boards that get a bit hot while >> building. I also use visionfive2 as my build machine. Quite happy with it. I have a fairly large heatsink installed without a fan, the temperature does not exceed 60 degrees at full load. > Cool, well let me know if any of those can be hooked up to the build > farm. It's quite easy and obviously you can still use them (and just > stop the build coordinator agent) if you need to. > I'd give it a try. Although now there is only a 256GB ssd plugged in and no dedicated ip address. I don't know how the coordinator works, maybe it doesn't matter, I need to see how it all works. -- Best regards, Aleksandr Vityazev
Re: RISC-V (riscv64-linux) substitutes are coming
On 2023-05-09, 16:41 +0100, Christopher Baines wrote: > Aleksandr Vityazev writes: > I've been having good luck with the visionfive1 as a build machine. My visionfive2 gets a little hot and I'm looking at getting a desk fan to blow at it and some of the other boards that get a bit hot while building. >> >> I also use visionfive2 as my build machine. Quite happy with it. I have >> a fairly large heatsink installed without a fan, the temperature does >> not exceed 60 degrees at full load. >> >>> Cool, well let me know if any of those can be hooked up to the build >>> farm. It's quite easy and obviously you can still use them (and just >>> stop the build coordinator agent) if you need to. >>> >> >> I'd give it a try. Although now there is only a 256GB ssd plugged in and >> no dedicated ip address. I don't know how the coordinator works, maybe >> it doesn't matter, I need to see how it all works. > > Cool :) 256GB is enough storage space, and there's no requirement for a > dedicated IP address. > I built guix-build-coordinator-agent-only version 0-75.d6ae42. Right now my system is on commit - 896982f357034e3e53fe05f86c416835adffda0c. Doing guix pull from 3f02f7d937a862d98367029e2d3506b228c6c80e, this will take a while. If the agent version is not important I can try to run the service. -- Best regards, Aleksandr Vityazev
Patch xdg-open in emacs-embark package
Just writing down a public TODO for myself: TODO: patch xdg-open (xdg-utils) in emacs-embark package. https://github.com/oantolin/embark/blob/f88314044d5492efeacb9466122889c6e60c8af4/embark.el#L3710 If anyone else wants to work on this feel free to.
