GNU bug report logs - #36649
27.0.50; pure space and pdumper

Previous Next

Full log

Message #208 received at 36649 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: eggert <at> cs.ucla.edu, rpluim <at> gmail.com, stefan <at> marxist.se,
 schwab <at> linux-m68k.org, pipcet <at> gmail.com, 36649 <at> debbugs.gnu.org, larsi <at> gnus.org,
 akrl <at> sdf.org
Subject: Re: bug#36649: 27.0.50; pure space and pdumper
Date: Wed, 12 May 2021 22:17:22 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: larsi <at> gnus.org,  pipcet <at> gmail.com,  eggert <at> cs.ucla.edu,
>   rpluim <at> gmail.com,  schwab <at> linux-m68k.org,  stefan <at> marxist.se,
>   36649 <at> debbugs.gnu.org,  akrl <at> sdf.org
> Date: Wed, 12 May 2021 15:07:42 -0400
> 
> > I just don't want to risk that, not at all.  Because if we are missing
> > something, it will require efforts I'd rather put elsewhere.
> 
> I can see a risk that removing purespace will break unexec because of
> some oversight of some detail somewhere (simply because it's
> a configuration that's basically never tested), but I can't imagine the
> breakage to be hard to fix: running without purespace has been used
> during the bootstrap for many many years, both with pdump and with
> unexec, so it's really not "special".

Last time I needed to fix a breakage in the unexec build it took a
non-trivial effort, and would have probably taken even more, had I not
been fortunate to have a user who could investigate the problems on
his own and present clear and correct causes of the problems.

So my bitter experience doesn't confirm your optimism.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.