public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Rob Landley <landley@trommello.org>
Cc: Anton Altaparmakov <aia21@cus.cam.ac.uk>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2-2.1.3 is available
Date: Tue, 15 Jan 2002 22:58:36 -0500	[thread overview]
Message-ID: <20020115225836.B4658@thyrsus.com> (raw)
In-Reply-To: <20020115145324.A5772@thyrsus.com> <Pine.SOL.3.96.1020115201156.26402C-100000@libra.cus.cam.ac.uk> <20020115152445.B6308@thyrsus.com> <20020116034147.CRIZ26021.femail12.sdc1.sfba.home.com@there>
In-Reply-To: <20020116034147.CRIZ26021.femail12.sdc1.sfba.home.com@there>; from landley@trommello.org on Tue, Jan 15, 2002 at 02:30:28PM -0500

Rob Landley <landley@trommello.org>:
> 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.)

Note, everyone else, that the freezing only happens on "make autoprobe".
The config.out that "make autoconfigure" writes is not frozen.
 
> 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 :).

Correction: menuconfig *does* save out frozen symbols, but it saves
them unfrozen.

> So just run menuconfig twice and you can edit everything that got
> autoprobed...

This "workaround" is entirely intentional.

> (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...)

Actually, this kind of cross-configuration is already fully supported.
The normal way of calling the configurator, through the Makefile,
passes -D$(ARCH) -- but if you call it without an architecture symbol
frozen by command-line option, architecture will be the first question
you're asked.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

All forms of government are pernicious, including good government.
	-- Edward Abbey

  reply	other threads:[~2002-01-16  4:15 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 19:53 CML2-2.1.3 is available 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
2002-01-16  3:58       ` Eric S. Raymond [this message]
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-22  6:29           ` Kai Henningsen
2002-01-23 21:45         ` Daniel Phillips
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
  -- strict thread matches above, loose matches on Subject: below --
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=20020115225836.B4658@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=aia21@cus.cam.ac.uk \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=landley@trommello.org \
    --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