From: Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 48024@debbugs.gnu.org, raingloom <raingloom@riseup.net>
Subject: bug#48024: glib-2.62.6 build fails i686
Date: Wed, 05 May 2021 12:34:30 -0400 [thread overview]
Message-ID: <87y2cti1gp.fsf@disroot.org> (raw)
In-Reply-To: <87eeennocl.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
Mark H Weaver writes:
> Did you also run "make"?
I have now.
> Hmm. Can you please grep the build log for "TIMEOUT" and
> "increase-test-timeout", and show me the matching lines?
"increase-test-timeout":
```
starting phase `increase-test-timeout'
phase `increase-test-timeout' succeeded after 0.1 seconds
```
"TIMEOUT":
```
53/259 glib:glib / rec-mutex TIMEOUT 120.03 s
83/259 glib:glib / 1bit-mutex TIMEOUT 120.02 s
84/259 glib:glib+slow / 1bit-emufutex TIMEOUT 180.05 s
```
Attached is the build log.
>>> (Incidentally, I *always* use Guix this way, using my own private branch
>>> of Guix, never using "guix pull", and never using substitutes.)
>>
>> This is interesting to me.
>
> I outlined how I use Guix in the following message:
>
> https://lists.gnu.org/archive/html/guix-devel/2021-03/msg00625.html
>
> However, note that there are some significant caveats and "rough edges"
> to this approach. I can't recommend it in good conscience, unless you
> truly need the extreme flexibility that it provides.
>
> To avoid the rough edges, I'd suggest using "guix pull --url" as
> outlined in the last two paragraphs of the message above. For most
> purposes, I suspect you'd be much happier with that approach.
Thank you for sharing this. Also thank you for the warning about 'significant caveats and "rough edges"'.
As a new user of Guix I think I will initially try to use the official
Guix repository.
However the message from Tobias Geerinckx-Rice in
https://issues.guix.gnu.org/48213 gives me the idea that your flexible
approach could be very useful if I find myself in a situation where I
have an issue that will not be addressed by an upstream project and
that has too much of a maintenance burden for Guix maintainers to take
on.
[-- Attachment #2: 1kqwp7fsdphlkg75x0bhyw5m49y41d-glib-2.62.6.drv.bz2 --]
[-- Type: application/octet-stream, Size: 26242 bytes --]
next prev parent reply other threads:[~2021-05-05 16:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 3:35 bug#48024: glib-2.62.6 build fails i686 Bone Baboon via Bug reports for GNU Guix
2021-04-26 15:26 ` raingloom
2021-04-27 19:25 ` Bone Baboon via Bug reports for GNU Guix
2021-04-28 3:23 ` Mark H Weaver
2021-05-03 22:00 ` Bone Baboon via Bug reports for GNU Guix
2021-05-04 0:38 ` Leo Famulari
2021-05-04 3:01 ` Mark H Weaver
2021-05-04 6:18 ` Efraim Flashner
2021-05-04 20:01 ` Mark H Weaver
2021-05-04 20:08 ` Mark H Weaver
2021-05-04 22:52 ` Bone Baboon via Bug reports for GNU Guix
2021-05-05 8:38 ` Efraim Flashner
2021-05-05 21:15 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 0:20 ` Mark H Weaver
2021-05-06 0:35 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 6:45 ` Efraim Flashner
2021-05-06 9:06 ` Bengt Richter
2021-05-06 17:44 ` Bone Baboon via Bug reports for GNU Guix
2021-05-07 17:46 ` Mark H Weaver
2021-05-08 13:26 ` Bengt Richter
2022-03-18 2:26 ` Maxim Cournoyer
2021-05-04 3:56 ` Mark H Weaver
2021-05-05 16:34 ` Bone Baboon via Bug reports for GNU Guix [this message]
2021-05-06 8:46 ` Mark H Weaver
2021-05-06 19:36 ` Bone Baboon via Bug reports for GNU Guix
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=87y2cti1gp.fsf@disroot.org \
--to=bug-guix@gnu.org \
--cc=48024@debbugs.gnu.org \
--cc=bone.baboon@disroot.org \
--cc=mhw@netris.org \
--cc=raingloom@riseup.net \
/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).