From: Michael Buesch <freesoftwaredeveloper@web.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make menuconfig error
Date: Mon, 31 Mar 2003 21:58:54 +0200 [thread overview]
Message-ID: <200303312158.54248.freesoftwaredeveloper@web.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0303311445140.11669-100000@dell>
> i'm pretty sure that, if you just unpacked the source for the
> first time, you should first "make mrproper" just to play it
> safe, and after that, you *must* do at least one full config
> of some kind, to create a number of header files that are
> necessary. the fact that you said you did a "make menuconfig",
> but bailed before you actually saved anything makes me uneasy.
buaaah, I'm very tired at the moment. :)
sorry for the question, problem is already solved and no
bug.
I'd better go to bed now. :)
Regards Michael Buesch.
next prev parent reply other threads:[~2003-03-31 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 19:34 make menuconfig error Michael Buesch
2003-03-31 19:47 ` Robert P. J. Day
2003-03-31 19:58 ` Michael Buesch [this message]
2003-03-31 20:40 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2003-06-20 20:27 David Christensen
2003-06-20 20:59 ` Michael Buesch
2003-06-20 21:08 ` Marc-Christian Petersen
2003-06-20 21:36 ` David Christensen
2003-06-20 21:42 ` Marc-Christian Petersen
2003-06-22 13:54 ` David Christensen
2001-10-02 13:51 make: *** [menuconfig] Error Sylvain Ravot
2001-10-02 15:26 ` Rasmus Bøg Hansen
2001-06-29 16:14 make menuconfig error axel
2001-04-21 3:59 Allen
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=200303312158.54248.freesoftwaredeveloper@web.de \
--to=freesoftwaredeveloper@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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.