From: Sam Ravnborg <sam@ravnborg.org>
To: "Mark Williams (MWP)" <mwp@internode.on.net>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: 2.6.10 make script problems
Date: Tue, 28 Dec 2004 00:36:24 +0100 [thread overview]
Message-ID: <20041227233624.GB9251@mars.ravnborg.org> (raw)
In-Reply-To: <20041227030142.GA3321@linux.comp>
On Mon, Dec 27, 2004 at 01:31:42PM +1030, Mark Williams (MWP) wrote:
>
> On a cleanly extracted 2.6.10 kernel, when i run "make menuconfig" i get the following:
>
> [root@linux linux-2.6.10]# make menuconfig
> HOSTCC scripts/basic/fixdep
> HOSTCC scripts/basic/split-include
> HOSTCC scripts/basic/docproc
> GEN /usr/src/linux-2.6.10-ck1/Makefile
> SHIPPED scripts/kconfig/zconf.tab.h
> HOSTCC scripts/kconfig/conf.o
> HOSTCC scripts/kconfig/mconf.o
> SHIPPED scripts/kconfig/zconf.tab.c
> SHIPPED scripts/kconfig/lex.zconf.c
> HOSTCC scripts/kconfig/zconf.tab.o
> HOSTLD scripts/kconfig/mconf
> HOSTCC scripts/lxdialog/checklist.o
> HOSTCC scripts/lxdialog/inputbox.o
> HOSTCC scripts/lxdialog/lxdialog.o
> HOSTCC scripts/lxdialog/menubox.o
> HOSTCC scripts/lxdialog/msgbox.o
> HOSTCC scripts/lxdialog/textbox.o
> HOSTCC scripts/lxdialog/util.o
> HOSTCC scripts/lxdialog/yesno.o
> HOSTLD scripts/lxdialog/lxdialog
>
> Note the "GEN /usr/src/linux-2.6.10-ck1/Makefile".
> Is this the problem?
Looks like you are using either make O= or have set KBUILD_OUTPUT to
/usr/src/linux-2.6.10-ck1.
But that does not explain it.
Where does the path "/usr/src/linux-2.6.10-ck1" come into the picture?
Sam
next prev parent reply other threads:[~2004-12-27 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 3:01 Mark Williams (MWP)
2004-12-27 23:36 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-26 14:53 Mark Williams (MWP)
2004-12-26 20:19 ` Sam Ravnborg
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=20041227233624.GB9251@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwp@internode.on.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®