From: Daniel Howe <dchowe@u.washington.edu>
To: linux-kernel@vger.kernel.org
Subject: Kernel build problem (2.4.1)...
Date: Wed, 02 May 2001 11:29:16 -0700 [thread overview]
Message-ID: <3AF051FC.21AFA1DB@u.washington.edu> (raw)
Greetings,
I'm having a problem with my running kernel (2.4.1) - attempting to make
a boot floppy. make bzDisk(& make bzImage) give the error below - any
ideas? Seems like bootsec is missing. I'm running Debian on x86...
thanks much,
/daniel
make[1]: Leaving directory `/usr/src/linux-2.4.1/arch/i386/lib'
ld -m elf_i386 -T /usr/src/linux-2.4.1/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.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 \
drivers/block/block.o drivers/char/char.o drivers/misc/misc.o
drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o
drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/cdrom/driver.o
drivers/sound/sounddrivers.o drivers/pci/driver.o
drivers/pcmcia/pcmcia.o drivers/net/pcmcia/pcmcia_net.o
drivers/pnp/pnp.o drivers/video/video.o \
net/network.o \
/usr/src/linux-2.4.1/arch/i386/lib/lib.a
/usr/src/linux-2.4.1/lib/lib.a /usr/src/linux-2.4.1/arch/i386/lib/lib.a
\
--end-group \
-o vmlinux
nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aUw]
\)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map
make[1]: Entering directory `/usr/src/linux-2.4.1/arch/i386/boot'
ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
ld: cannot open binary: No such file or directory
make[1]: *** [bbootsect] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.1/arch/i386/boot'
make: *** [bzImage] Error 2
next reply other threads:[~2001-05-02 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 18:29 Daniel Howe [this message]
2001-05-02 18:52 ` Kernel build problem (2.4.1) Mohammad A. Haque
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=3AF051FC.21AFA1DB@u.washington.edu \
--to=dchowe@u.washington.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.