From: Tomas Szepe <szepe@pinerecords.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: linux kernel conf 0.7
Date: Sat, 28 Sep 2002 16:42:50 +0200 [thread overview]
Message-ID: <20020928144250.GC3337@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209281529580.338-100000@serv>
> At http://www.xs4all.nl/~zippel/lc/ you can find the latest version of the
> new config system. Besides the usual archive there is also now a patch
> against a 2.5.39 kernel and finally some documentation.
o lkc-0.7-2.5.39.diff includes patches to include/linux/autoconf.h
o 'make distclean; make oldconfig' produces
make[1]: Entering directory /usr/src/linux-2.5.39/scripts/lkc'
Makefile:42: *** missing separator (did you mean TAB instead of 8 spaces?). Stop.
make[1]: Leaving directory /usr/src/linux-2.5.39/scripts/lkc'
make: *** [oldconfig] Error 2
i.e. the patch seems to have foomed up the tabs
o fix up & continue, 'make distclean; make oldconfig' produces
kala@kirsi:/usr/src/linux-2.5.39$ make oldconfig
make[1]: Entering directory /usr/src/linux-2.5.39/scripts/lkc'
cat zconf.tab.h_shipped > zconf.tab.h
gcc -Wp,-MD,./.conf.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o conf.o conf.c
/bin/sh: /usr/src/linux-2.5.39/scripts/fixdep: No such file or directory
make[1]: *** [conf.o] Error 1
make[1]: Leaving directory /usr/src/linux-2.5.39/scripts/lkc'
make: *** [oldconfig] Error 2
And so on.
T.
next prev parent reply other threads:[~2002-09-28 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 14:25 Roman Zippel
2002-09-28 14:42 ` Tomas Szepe [this message]
2002-09-28 15:15 ` Roman Zippel
2002-09-28 15:41 ` Roman Zippel
2002-09-28 22:48 ` Sam Ravnborg
2002-09-29 0:00 ` 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=20020928144250.GC3337@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®