From: Matthieu Haefele <matthieu.haefele@cnrs.fr>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 58149@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: bug#58149: guix pull error
Date: Wed, 5 Oct 2022 16:36:25 +0200 [thread overview]
Message-ID: <47084b8f-385e-46cc-c85f-010001d12b50@cnrs.fr> (raw)
In-Reply-To: <87y1tusjfu.fsf@inria.fr>
[-- Attachment #1.1.1: Type: text/plain, Size: 1778 bytes --]
Sorry I overlooked your last answer
Le 05/10/2022 à 11:34, Ludovic Courtès a écrit :
>
>> collect2: error: ld returned 1 exit status
>> make[2]: *** [../../gcc-5.5.0/gcc/c/Make-lang.in:71: cc1] Error 1
> I don’t see an error message in the snippet you pasted. Could it be
> OOM, or was there a clue in /var/log/messages or similar?
Out of memory is a possibility, I am running all this on my small laptop, but retried it closing everything else and failed again.
/var/log/syslog are attached. Except the rise of temperature cores, there is no error appearing here. But I am maybe looking at
the wrong place, I am a pretty bad sys admin :~
>> Thanks for diving in this ocean of code and trying to make it manageable with a reproducible process to build it :)
> That’s an insightful exercise for sure. :-)
Wow, just an /exercise/ for you !? What will it be when you will start to really work then ;)
>
>> BTW I am watching the videos of the very interesting event organized
>> for the ten years of guix. The presentation of Efraim Flashner stunted
>> me. 40h of compile just for rust from the bootstrap on a RISC-V but
>> still GHz processor. How can these things work in the end ... ? Life,
>> as the single negentropic known process should play its role here as
>> well. The minimalism wished by Pjotr Prins is the way to go if we want
>> to keep the illusion of controlling what we are doing.
> The bootstrapping effort is about “regaining control” of our software
> stack in a way, but it shows just how much things had gotten awry.
>
Fair enough. Still, it makes sense to invest time and energy on the topic even if I am definitely not the skilled guy for it !! I
am just an humble application developer able to use it and report bugs ;)
Thanks
Mat
[-- Attachment #1.1.2: Type: text/html, Size: 2862 bytes --]
[-- Attachment #1.2: log.bz2 --]
[-- Type: application/x-bzip, Size: 3305 bytes --]
[-- Attachment #2: Signature cryptographique S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4270 bytes --]
next prev parent reply other threads:[~2022-10-05 14:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 15:47 bug#58149: guix pull error Matthieu Haefele
2022-09-28 22:06 ` zimoun
2022-09-29 13:37 ` Ludovic Courtès
2022-09-29 15:04 ` Matthieu Haefele
2022-09-29 15:15 ` Ludovic Courtès
2022-09-29 15:35 ` Matthieu Haefele
2022-09-29 17:55 ` Maxime Devos
2022-09-30 6:09 ` Matthieu Haefele
2022-09-30 7:59 ` Ludovic Courtès
2022-09-30 9:42 ` Matthieu Haefele
2022-10-03 9:04 ` bug#58149: Letting clients warn about old daemons Ludovic Courtès
2022-10-03 15:12 ` Maxim Cournoyer
2022-10-03 9:17 ` bug#58149: guix pull error Ludovic Courtès
2022-10-03 9:33 ` Matthieu Haefele
2022-10-03 14:03 ` Ludovic Courtès
2022-10-03 14:49 ` Matthieu Haefele
2022-10-04 10:11 ` Ludovic Courtès
2022-10-04 13:01 ` Matthieu Haefele
2022-10-05 9:34 ` Ludovic Courtès
2022-10-05 10:47 ` Matthieu Haefele
2022-10-05 10:52 ` Matthieu Haefele
2022-10-05 15:02 ` zimoun
2022-10-05 15:08 ` Matthieu Haefele
2022-10-06 8:47 ` Ludovic Courtès
2022-10-06 10:10 ` Matthieu Haefele
2022-10-06 10:30 ` zimoun
2022-10-06 12:14 ` Matthieu Haefele
2022-10-06 13:56 ` zimoun
2022-10-06 15:15 ` Matthieu Haefele
2022-10-06 15:38 ` zimoun
2022-10-06 16:00 ` Maxime Devos
2022-10-06 16:01 ` Ludovic Courtès
2022-10-06 10:57 ` Maxime Devos
2022-10-06 12:08 ` Matthieu Haefele
2022-10-06 15:56 ` Maxime Devos
2022-10-06 15:58 ` Ludovic Courtès
2022-10-05 14:36 ` Matthieu Haefele [this message]
2022-10-07 2:40 ` bokr
2022-10-14 12:19 ` zimoun
2022-10-03 20:47 ` bug#58149: Unable to pull when using a pre-lzip version of guix-daemon Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47084b8f-385e-46cc-c85f-010001d12b50@cnrs.fr \
--to=matthieu.haefele@cnrs.fr \
--cc=58149@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).