From: Sam Ravnborg <sam@ravnborg.org>
To: Voicu Liviu <pacman@mscc.huji.ac.il>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: make menuconfig
Date: Sun, 27 Jul 2003 16:26:37 +0200 [thread overview]
Message-ID: <20030727142637.GA11649@mars.ravnborg.org> (raw)
In-Reply-To: <3F239AE5.9010403@mscc.huji.ac.il>
On Sun, Jul 27, 2003 at 12:27:01PM +0300, Voicu Liviu wrote:
> >
> >Works for me. Could you provide exact error-message etc.
>
> liviu@starshooter liviu $ su
> Password:
> liviu has logged on pts/0 from :0.0.
> liviu has logged on pts/1 from :0.0.
> liviu has logged on vc/1 from local.
> liviu has logged on vc/2 from local.
> starshooter /root# cd /usr/src/linux
> starshooter src/linux# make menuconfig
> Missing }.
> starshooter src/linux#
Too little context to determine where it goes wrong.
I tried with tcsh here with success.
Try the followings steps:
1) Do not compile as root. In general does as little as possible as root.
Only the kernel installlation requires root priviliges.
2) Try to run "make -n", that may hint where is goes wrong.
3) Do not locate the kernel src in /usr/src/linux - it will conflict with
glibc header files. No matter what a HOWTO say otherwise.
4) Try another shell, for instance bash.
Not that the kernel build should rely on bash only, but an approach to
get your kernel to compile.
Sam
next prev parent reply other threads:[~2003-07-27 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 8:48 make menuconfig Voicu Liviu
2003-07-27 10:00 ` Sam Ravnborg
2003-07-27 9:27 ` Voicu Liviu
2003-07-27 14:26 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-14 11:34 Nick Warne
2005-02-14 12:12 ` Roman Zippel
2005-02-14 12:27 ` Nick Warne
2005-02-14 12:45 ` Roman Zippel
2005-02-14 21:55 ` Nick Warne
2002-10-02 7:53 Michael Knigge
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=20030727142637.GA11649@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pacman@mscc.huji.ac.il \
/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;
as well as URLs for NNTP newsgroup(s).