From: Andrei Mikhailovsky <andrei@arhont.com>
To: Brice Goglin <Brice.Goglin@ens-lyon.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 make menuconfig error
Date: Fri, 09 Jan 2004 23:46:35 +0000 [thread overview]
Message-ID: <3FFF3D5B.7040601@arhont.com> (raw)
In-Reply-To: <20040109141455.GJ4485@ens-lyon.fr>
Yeah, it happens to me to. The same problem happens with -mm1 patch.
Andrei
Brice Goglin wrote:
> Hi,
>
> When configuring 2.6.1 with make menuconfig,
> if I choose not to save my configuration changes,
> I get this error:
>
>
> puligny:~/build/linux-2.6.1% make menuconfig
> make[1]: scripts/fixdep' is up to date.
> scripts/kconfig/mconf arch/i386/Kconfig
> #
> # using defaults found in .config
> #
>
>
> Your kernel configuration changes were NOT saved.
>
> make[1]: *** [menuconfig] Error 1
> make: *** [menuconfig] Error 2
> puligny:~/build/linux-2.6.1%
>
>
> 2.6.0 does not show such two error lines.
>
> Best regards.
next prev parent reply other threads:[~2004-01-09 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 14:14 2.6.1 make menuconfig error Brice Goglin
2004-01-09 23:46 ` Andrei Mikhailovsky [this message]
2004-01-10 2:51 ` Roman Zippel
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=3FFF3D5B.7040601@arhont.com \
--to=andrei@arhont.com \
--cc=Brice.Goglin@ens-lyon.fr \
--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