From: Mike Gerwitz <mtg@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 43610@debbugs.gnu.org
Subject: bug#43610: IceCat segfault
Date: Wed, 30 Sep 2020 21:56:04 -0400 [thread overview]
Message-ID: <875z7uvhe3.fsf@gnu.org> (raw)
In-Reply-To: <87blhs8lb7.fsf@netris.org> (Mark H. Weaver's message of "Sat, 26 Sep 2020 14:05:53 -0400")
On Sat, Sep 26, 2020 at 14:05:53 -0400, Mark H Weaver wrote:
> I'm particularly sensitive to the memory requirements at build time,
> because I choose not to trust the build farm and therefore to build my
> entire Guix system with GNOME from source code on a relatively old
> Thinkpad X200 with only 4 GB of RAM. I've been doing this for many
> years, and I'd like to enable other Guix users to do so if they wish.
As someone with the same system as you, I have appreciated this for
as long as I've used Guix. Thank you.
> My impression is that IceCat debug outputs would primarily useful to
> people who are actively developing IceCat, in which case it makes more
> sense to build it manually to allow incremental rebuilds after modifying
> the source code.
I agree---I think it's best not to burden all users (that choose to or
have to build) in this case.
--
Mike Gerwitz
next prev parent reply other threads:[~2020-10-01 1:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 13:26 bug#43610: IceCat segfault raingloom
2020-09-25 16:11 ` Mark H Weaver
2020-09-26 2:34 ` raingloom
2020-09-26 18:05 ` Mark H Weaver
2020-09-27 5:49 ` raingloom
2020-09-27 20:36 ` Mark H Weaver
2020-10-01 22:57 ` raingloom
2020-10-01 23:28 ` raingloom
2020-10-09 7:42 ` Ricardo Wurmus
2020-11-30 20:06 ` Ricardo Wurmus
2020-11-30 20:12 ` Ricardo Wurmus
2020-12-13 18:19 ` Alex ter Weele
2020-12-15 11:24 ` Ludovic Courtès
2022-07-11 18:38 ` Maxim Cournoyer
2020-10-01 1:56 ` Mike Gerwitz [this message]
2023-04-07 16:14 ` bug#43610: Segfault still an issue Dominik Delgado via Bug reports for GNU Guix
2023-04-08 7:55 ` Dominik Delgado 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=875z7uvhe3.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=43610@debbugs.gnu.org \
--cc=mhw@netris.org \
/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).