From: "Eric S. Raymond" <esr@thyrsus.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] CML2 1.9.7 is available
Date: Thu, 13 Dec 2001 03:41:35 -0500 [thread overview]
Message-ID: <20011213034135.A8267@thyrsus.com> (raw)
In-Reply-To: <20011212023556.A8819@thyrsus.com> <16992.1008153373@ocs3.intra.ocs.com.au>
In-Reply-To: <16992.1008153373@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Wed, Dec 12, 2001 at 09:36:13PM +1100
Keith Owens <kaos@ocs.com.au>:
> Dangling symlink kernel-tree/scripts/tree.py breaks the CML2 install,
> rm kernel-tree/scripts/tree.py first.
Fixed.
> There are still discrepancies between the output produced by different
> forms of make *config. I am also seeing spurious deduction messages
> which may be related or may be a separate problem.
Separate problem.
> Why are those deduction messages appearing in menuconfig? I just did
> make oldconfig, the config should be stable. I did not change anything
> in menuconfig, just saved it.
The deduction messages are happening because the side-effect forcing
logic fires whenever a symbol is set. It has no way of knowing
whether or not the forced symbol will occur later in the config being read.
This
> Why is the output after menuconfig WITH NO CHANGES different from
> the oldconfig that went into menuconfig?
I think it's because of the different timing of menu visits (forcing computation
of choice-menu defaults at different times). I'm going to run some experiments
to see if I can pin this down.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
"The state calls its own violence `law', but that of the individual `crime'"
-- Max Stirner
next prev parent reply other threads:[~2001-12-13 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 7:35 CML2 1.9.7 is available Eric S. Raymond
2001-12-12 10:36 ` [kbuild-devel] " Keith Owens
2001-12-13 8:41 ` Eric S. Raymond [this message]
2001-12-13 8:49 ` Eric S. Raymond
2001-12-13 16:29 ` Bjorn Helgaas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011213034135.A8267@thyrsus.com \
--to=esr@thyrsus.com \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.