From: Rob Landley <landley@trommello.org>
To: esr@thyrsus.com, Anton Altaparmakov <aia21@cus.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2-2.1.3 is available
Date: Tue, 15 Jan 2002 14:30:28 -0500 [thread overview]
Message-ID: <20020116034147.CRIZ26021.femail12.sdc1.sfba.home.com@there> (raw)
In-Reply-To: <20020115145324.A5772@thyrsus.com> <Pine.SOL.3.96.1020115201156.26402C-100000@libra.cus.cam.ac.uk> <20020115152445.B6308@thyrsus.com>
In-Reply-To: <20020115152445.B6308@thyrsus.com>
On Tuesday 15 January 2002 03:24 pm, Eric S. Raymond wrote:
> To invoke the autoconfigurator, you do one of two things:
>
> `make autoconfigure'
> This runs the autoconfigurator in standalone mode. This gives you
> an entire configuration, ready to build with.
>
> `make autoprobe {config,menuconfig,xconfig}'
> This runs the autoconfigurator in probe mode, which gives you
> a report on facilities found (without making assumptions about facilities
> not found). This report gets fed to your interactive configurator, which
> then proceeds not to bother you with questions for which the autoprobe
> report already gave it answers.
>
> The ordinary make {config,menuconfig,xconfig} behaves as it always did.
Eric and I disagree on the behavior of "make autoprobe". He likes the
concept of "freezing" symbols, which says if the autoprober detected a
configuration setting, the question shouldn't show up and give you the
opportunity to disagree. (Not confusing Aunt Tillie, with her LCSE from
CompTIA (and apparently has recently moved in with Alan Cox), with questions
that she's more likely to screw up than improve.)
Personally, I think that if you turn on "expert" mode, you should be able to
override anything. I haven't complained much because there is an easy
workaround: Although the autoprober puts the "frozen" flag on the symbols it
finds, menuconfig doesn't save them out :). So just run menuconfig twice and
you can edit everything that got autoprobed...
The user interface still has a couple of teething troubles, but they're
mostly in the new stuff that CML1 never attempted to do (like autoconfig).
(Now the standard configuration DOES freeze, and therefore hide, the "which
architecture am I building for" question. It would be nice if "make
menuconfig" would let you do a cross-compile simply by selecting your
architecture. I understand why this isn't supported though: to properly
build most architectures other than X86, you have to apply patches to Linus's
tree. And the make would have to tell gcc to cross-compile, which most gcc
builds don't know how to do and the makefiles don't seem to support
anyway...)
Rob
next prev parent reply other threads:[~2002-01-16 3:45 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 19:53 Eric S. Raymond
2002-01-15 20:15 ` Nicolas Pitre
2002-01-15 20:18 ` Eric S. Raymond
2002-01-15 20:41 ` Nicolas Pitre
2002-01-15 19:19 ` Rob Landley
2002-01-16 3:48 ` Eric S. Raymond
2002-01-16 6:29 ` Peter Samuelson
2002-01-16 6:32 ` Eric S. Raymond
2002-01-16 7:13 ` Peter Samuelson
2002-01-16 6:36 ` Alexander Viro
2002-01-16 0:15 ` Henning P. Schmiedehausen
2002-01-15 20:16 ` Anton Altaparmakov
2002-01-15 20:24 ` Eric S. Raymond
2002-01-15 19:30 ` Rob Landley [this message]
2002-01-16 3:58 ` Eric S. Raymond
2002-01-15 20:25 ` Russell King
2002-01-15 19:37 ` Rob Landley
2002-01-17 1:18 ` Val Henson
2002-01-21 16:22 ` Daniel Phillips
2002-01-21 17:05 ` [kbuild-devel] " Giacomo Catenazzi
2002-01-21 23:11 ` Daniel Phillips
2002-01-23 21:45 ` Daniel Phillips
2002-01-22 6:29 ` Kai Henningsen
2002-01-16 0:38 ` Peter Samuelson
2002-01-15 20:26 ` Ross Vandegrift
2002-01-16 4:02 ` Eric S. Raymond
2002-01-16 16:38 ` Ross Vandegrift
2002-01-16 16:59 ` Ross Vandegrift
2002-01-16 18:29 ` Rob Landley
2002-01-18 18:32 ` Ross Vandegrift
2002-01-22 5:31 ` Eric S. Raymond
2002-01-15 20:27 ` Robert Love
2002-01-15 21:09 ` David Lang
2002-01-16 15:06 ` Horst von Brand
2002-01-16 21:31 ` Eric S. Raymond
2002-01-16 21:56 ` Horst von Brand
2002-01-16 21:47 ` Eric S. Raymond
2002-01-17 1:26 ` David Woodhouse
2002-01-17 1:43 ` Eric S. Raymond
2002-01-17 8:53 ` David Woodhouse
2002-01-17 13:37 ` Eric S. Raymond
2002-01-17 14:09 ` David Woodhouse
2002-01-17 14:29 ` Eric S. Raymond
2002-01-16 23:36 ` David Lang
2002-01-18 6:48 ` Kai Henningsen
2002-01-22 9:11 [kbuild-devel] " Giacomo Catenazzi
2002-01-22 9:20 ` Keith Owens
[not found] <fa.d4sn1fv.b78io8@ifi.uio.no>
[not found] ` <fa.i3p6mlv.1mg2frl@ifi.uio.no>
2002-01-22 10:09 ` Giacomo Catenazzi
2002-01-22 10:25 ` Keith Owens
2002-01-22 10:48 ` Giacomo Catenazzi
2002-01-22 10:53 ` Keith Owens
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=20020116034147.CRIZ26021.femail12.sdc1.sfba.home.com@there \
--to=landley@trommello.org \
--cc=aia21@cus.cam.ac.uk \
--cc=esr@thyrsus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®