From: Kevin Corry <corryk@us.ibm.com>
To: GrandMasterLee <masterlee@digitalroadkill.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: EVMS breaking menuconfig in 2.5.40?
Date: Mon, 7 Oct 2002 09:30:20 -0500 [thread overview]
Message-ID: <02100709302000.15613@boiler> (raw)
In-Reply-To: <1033968519.3948.7.camel@localhost>
On Monday 07 October 2002 00:28, GrandMasterLee wrote:
> I got EVMS from cvs, found the 2.5.40 patch, applied it, then attempted
> to do make menuconfig.
>
> All that happens is this:
>
> [austin@UberGeek linux-2.5.40]$ make menuconfig
> make[1]: Entering directory `/data/build/linux-2.5.40/scripts'
> make -C lxdialog all
> make[2]: Entering directory `/data/build/linux-2.5.40/scripts/lxdialog'
> make[2]: Leaving directory `/data/build/linux-2.5.40/scripts/lxdialog'
> make[1]: Leaving directory `/data/build/linux-2.5.40/scripts'
> /bin/sh ./scripts/Menuconfig arch/i386/config.in
> Using defaults found in .config
> Preparing scripts: functions, parsing
It sounds like you added the EVMS common-files patch but not the actual EVMS
code. This will cause the kernel config to break, since it can't find the
file drivers/evms/Config.in.
If you want to build the latest EVMS kernel code from CVS, please see
http://evms.sf.net/install.html (last section).
> and then my console becomes unuseable, I can't even ssh in from another
> box, then X dies eventually.
>
> If I hit and hold ctrl-c for a few seconds after this begins, I can
> usually break out, but if I miss it, then well, X blows up pretty good.
This doesn't make much sense. When I reproduce the above situation, all I get
is an error from awk, and then make quits with an error. I can't imagine why
it would cause your X server to blow up.
--
Kevin Corry
corryk@us.ibm.com
http://evms.sourceforge.net/
prev parent reply other threads:[~2002-10-07 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 5:28 EVMS breaking menuconfig in 2.5.40? GrandMasterLee
2002-10-07 14:30 ` Kevin Corry [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=02100709302000.15613@boiler \
--to=corryk@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masterlee@digitalroadkill.net \
/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.