From: Adrian Bunk <bunk@fs.tum.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: kbuild-devel <kbuild-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux kernel conf 0.9
Date: Tue, 15 Oct 2002 15:35:23 +0200 (CEST) [thread overview]
Message-ID: <Pine.NEB.4.44.0210151528310.20607-100000@mimas.fachschaften.tu-muenchen.de> (raw)
In-Reply-To: <3DAB23CB.5B52ECF1@linux-m68k.org>
Hi Roman,
I do always get the following segfault:
<-- snip -->
$ cd /tmp/
$ tar xzf lkc-0.9.tar.gz
$ cd lkc-0.9
$ make
...
$ cd ~/linux/kernel-2.5
$ tar xzf linux-2.5.42.tar.gz
$ cd linux-2.5.42
$ bzcat /tmp/lkc-0.9-2.5.42.diff.bz2 |patch -p1
...
$ /tmp/lkc-0.9/lkcc i386
...
undefined symbol ARCH_ACORN
undefined symbol IA64
undefined symbol BAGET_MIPS
undefined symbol IA32_EMULATION
undefined symbol RPXCLASSIC
undefined symbol IT8172_REVC
recursive dependency: ISDN_DRV_EICON_DIVAS ISDN_DRV_EICON_OLD (choice(2) detected) ISDN_DRV_EICON_DIVAS
recursive dependency: AEDSP16_MSS AEDSP16_SBPRO (choice(1) detected) AEDSP16_MSS
recursive dependency: INPUT_GAMEPORT INPUT_GAMEPORT
recursive dependency: SCSI_AIC7XXX_OLD SCSI_AIC7XXX (choice(2) detected) SCSI_AIC7XXX_OLD AIC7XXX_BUILD_FIRMWARE
Segmentation fault
$
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2002-10-15 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 20:06 linux kernel conf 0.9 Roman Zippel
2002-10-14 20:40 ` [kbuild-devel] " Greg KH
2002-10-14 21:00 ` Roman Zippel
2002-10-15 13:35 ` Adrian Bunk [this message]
2002-10-15 13:56 ` Roman Zippel
2002-10-15 14:01 ` Roman Zippel
2002-10-15 14:24 ` Adrian Bunk
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=Pine.NEB.4.44.0210151528310.20607-100000@mimas.fachschaften.tu-muenchen.de \
--to=bunk@fs.tum.de \
--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;
as well as URLs for NNTP newsgroup(s).