David Relson <[email protected]>:
> From past testing of CML2 I know it uses file config.out as its
> "memory". Looking in it, I didn't see any CONFIG symbols for these symbols.
>
> There's definitely something here for Eric to fix!
I'm on it.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Live free or die; death is not the worst of evils.
-- General George Stark.
I found it!
The culprit: a bit of confusion over 'private'.
All of the not-saved symbols were just guards for 'do we
want to display question X'... so they were marked
private, so as not to clutter up the kernel (I assume).
However, this prevents them from getting written to
.config/config.out as well! Easy fix is to un-private
them, long-term is (as I see it) either to create a new
equivalent to private that somehow lets the symbol get
written to defconfig, but prevents it from becoming a
kernel define, or just to blow it off and don't worry
about it, and leave them normal symbols. However, it's
1:30AM and I might be missing something.
--Andrew
On Wed, 2 Jan 2002 10:03:11 -0500
"Eric S. Raymond" <[email protected]> wrote:
> David Relson <[email protected]>:
> > From past testing of CML2 I know it uses file
> config.out as its
> > "memory". Looking in it, I didn't see any CONFIG
> symbols for these symbols.
> >
> > There's definitely something here for Eric to fix!
>
> I'm on it.
> --
> <a href="http://www.tuxedo.org/~esr/">Eric S.
> Raymond</a>
>
> Live free or die; death is not the worst of evils.
> -- General George Stark.
Andrew Rodland <[email protected]>:
> I found it!
> The culprit: a bit of confusion over 'private'.
> All of the not-saved symbols were just guards for 'do we
> want to display question X'... so they were marked
> private, so as not to clutter up the kernel (I assume).
> However, this prevents them from getting written to
> .config/config.out as well! Easy fix is to un-private
> them, long-term is (as I see it) either to create a new
> equivalent to private that somehow lets the symbol get
> written to defconfig, but prevents it from becoming a
> kernel define, or just to blow it off and don't worry
> about it, and leave them normal symbols. However, it's
> 1:30AM and I might be missing something.
I think the right thing will be to write private symbols into config.out,
but with an attached PRIVATE label that stops configtrans.py from
translating these into defines for the autoconf.h file.
That's what I've done for the upcoming CML 2.0.0 release.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Question with boldness even the existence of a God; because, if there
be one, he must more approve the homage of reason, than that of
blindfolded fear.... Do not be frightened from this inquiry from any
fear of its consequences. If it ends in the belief that there is no
God, you will find incitements to virtue in the comfort and
pleasantness you feel in its exercise...
-- Thomas Jefferson, in a 1787 letter to his nephew
After sleep and further thought, that makes perfect sense.
On Thu, 3 Jan 2002 02:31:05 -0500
"Eric S. Raymond" <[email protected]> wrote:
> I think the right thing will be to write private symbols
> into config.out,
> but with an attached PRIVATE label that stops
> configtrans.py from
> translating these into defines for the autoconf.h file.
>
> That's what I've done for the upcoming CML 2.0.0 release.
> --