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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: luangruo <at> yahoo.com, 36649 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, pipcet <at> gmail.com
Subject: bug#36649: 27.0.50; pure space and pdumper
Date: Sat, 02 Jul 2022 15:45:18 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  pipcet <at> gmail.com,  36649 <at> debbugs.gnu.org,
>   monnier <at> iro.umontreal.ca
> Date: Sat, 02 Jul 2022 14:41:01 +0200
> 
> > unexec isn't doing any harm by itself, so there's no reason to not keep
> > it.  I don't forsee much trouble in keeping pure space behind a few
> > ifdefs; it should be a mostly mechanical job.
> 
> But Eli doesn't want to get rid of purespace (which we do want to) until
> we get rid of unexec, so unexec is blocking progress in that sense.

No, I'm okay with having the purespace removed from the pdumper
builds, if the unexec build can still use it.  AFAIU, that's the
"behind several ifdefs" alternative.

Previous Next

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