linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Funderburg (at home)" <Chris@Funderburg.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.32
Date: Tue, 27 Aug 2002 23:28:04 +0100	[thread overview]
Message-ID: <3D6BFCF4.8010909@Funderburg.com> (raw)
In-Reply-To: Pine.LNX.4.33.0208271239580.2564-100000@penguin.transmeta.com

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]


This is the closest I've come to actually being able to compile a kernel 
 > 2.5.25 yet...

But there seems to be one more problem at the very end:

   ld -m elf_i386  -r -o init.o main.o version.o do_mounts.o
make[1]: Leaving directory `/usr/src/linux-2.5.32/init'
  ld -m elf_i386 -T arch/i386/vmlinux.lds -e stext 
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/init.o 
--start-group arch/i386/kernel/kernel.o arch/i386/mm/mm.o 
kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o security/built-in.o 
/usr/src/linux-2.5.32/arch/i386/lib/lib.a lib/lib.a 
/usr/src/linux-2.5.32/arch/i386/lib/lib.a drivers/built-in.o 
sound/sound.o arch/i386/pci/pci.o net/network.o --end-group -o vmlinux
net/network.o: In function `register_8022_client':
net/network.o(.text+0xf59f): undefined reference to `llc_sap_open'
net/network.o: In function `unregister_8022_client':
net/network.o(.text+0xf5ca): undefined reference to `llc_sap_close'
net/network.o: In function `snap_init':
net/network.o(.text.init+0x59d): undefined reference to `llc_sap_open'
make: *** [vmlinux] Error 1

Something missing an "include", or just some dodgy .config ???




[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2845 bytes --]

  parent reply	other threads:[~2002-08-27 22:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 19:47 Linux v2.5.32 Linus Torvalds
2002-08-27 20:22 ` Stephane Wirtel
2002-08-27 20:36   ` Thunder from the hill
2002-08-27 20:48     ` Stephane Wirtel
2002-08-27 20:54   ` Gabor Z. Papp
2002-08-28  6:18     ` Jan-Benedict Glaw
2002-08-28  7:41       ` Edward Coffey
2002-08-28  8:35       ` Russell King
2002-08-27 20:43 ` Udo A. Steinberg
2002-08-27 20:47   ` Andre Hedrick
2002-08-27 20:47   ` Alexander Viro
2002-08-27 22:35     ` Alan Cox
2002-08-28  2:07       ` [PATCH] " Alexander Viro
2002-08-28  1:21     ` Arador
2002-08-28  2:17       ` Alexander Viro
2002-08-27 22:28 ` Chris Funderburg (at home) [this message]
2002-08-28  7:31 ` Linux v2.5.32 - some menuconfig oddities Helge Hafting
2002-08-28  7:43   ` Gabor Kerenyi
2002-08-28  8:14 ` Linux v2.5.32 Edward Coffey
2002-08-28  8:17   ` Writing files to remote storage Kevin Liao
2002-08-28 14:18     ` Alan Cox
2002-08-28 13:00 ` 2.5.32 doesn't beep? Mikael Pettersson
2002-08-28 13:05   ` Vojtech Pavlik
2002-08-28 13:12     ` Mikael Pettersson
2002-08-28 13:58     ` Gerhard Mack
2002-08-28 14:33       ` Jos Hulzink
2002-08-28 14:49       ` Vojtech Pavlik
2002-08-28 20:04     ` Mikael Pettersson
2002-08-28 20:30       ` Vojtech Pavlik
2002-08-29  8:41         ` Gerd Knorr
2002-08-28 17:21 ` Linux v2.5.32 Adrian Bunk
2002-08-31 16:54 ` Linux v2.5.32 (Config options to have a working keyboard) Axel Siebenwirth
2002-08-27 23:50 Linux v2.5.32 Michel Eyckmans (MCE)
2002-08-28  0:43 rwhron
2002-08-28  1:15 ` Andre Hedrick
2002-08-28  2:21   ` Alexander Viro

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=3D6BFCF4.8010909@Funderburg.com \
    --to=chris@funderburg.com \
    --cc=linux-kernel@vger.kernel.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).