mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Lukasz Stelmach <stlman@poczta.fm>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: make oldconfig problem Re: autoconf.h and auto.conf missing
Date: Wed, 29 Nov 2006 14:20:41 +0000	[thread overview]
Message-ID: <1164810041.13736.3.camel@localhost.localdomain> (raw)
In-Reply-To: <456B6B02.9060105@poczta.fm>

On Mon, 2006-11-27 at 23:47 +0100, Lukasz Stelmach wrote:
> Greetings.
> 
> It seems that someone has broken *conf programs in 2.6.18 because
> only "make silentoldconfig" recreates autoconf.h and auto.conf
> properly after configuration (.config) has changed.
> 
> I do everything as I always have done.
> 1. create an empty dir and put my current .config there
> 2. make O=dir oldconfig
> 3. compile, everything seems to be OK here
> 4. do some changes to .config and make oldconfig once again
> BZZZZZT

yap I have the same problem 

to workaround I just do make xconfig and click on save.

I like to have some more input about this ....

Thanks, 
> 5. auto.conf and autoconf.h don't change along with .config and when
>  I build the kernel once again new settings don't take effect.
> 
> I discovered I have to make silentoldconfig to regenerate autoconf
> files. However, this *seems* to force rebuilding of all the objects
> instead of, what it has always done, only those that depend on
> altered configurations.
> 
> Has anyone else seen something like this? Is it a bug or a feature?
> 
> Best regards,
> 
> Please CC, I am not a subscriber.


      parent reply	other threads:[~2006-11-29 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 22:47 Lukasz Stelmach
2006-11-28 11:19 ` Roman Zippel
2006-11-29 14:20 ` Sergio Monteiro Basto [this message]

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=1164810041.13736.3.camel@localhost.localdomain \
    --to=sergio@sergiomb.no-ip.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stlman@poczta.fm \
    /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

Powered by JetHome