linux-8086.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derek Johansen <djohanse678@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: build.sh errors when enabling kernel hacking -> system trace
Date: Wed, 22 Mar 2017 21:51:52 -0600	[thread overview]
Message-ID: <CAOv0vdncUa_RmHkXKnaN_U=cA+-6kR9dOUm6OY3Oj5t_ucLa1g@mail.gmail.com> (raw)

Running sudo ./build.sh

when the menu comes up to select the configuration options I select:

kernel hacking -> system trace

The build script errors out as follows:

ld86 -0 -M  -s -o boot/bootsect boot/bootsect.o > boot/bootsect.map
ld86 -0 -M  -s -o boot/setup boot/setup.o > boot/setup.map
(cd ../.. ; ld86 -0 -i  -t -M  \
arch/i86/boot/crt0.o arch/i86/boot/crt1.o \
init/main.o kernel/kernel.a fs/fs.a lib/lib.a net/net.a
fs/minix/minixfs.a arch/i86/kernel/akernel.a arch/i86/lib/lib86.a
arch/i86/mm/mm.a  arch/i86/drivers/char/chr_drv.a
arch/i86/drivers/block/blk_drv.a arch/i86/drivers/net/net_drv.a \
-o arch/i86/boot/system > arch/i86/boot/system.tmp ; \
sort -k4 arch/i86/boot/system.tmp > arch/i86/boot/system.map ; \
rm -f arch/i86/boot/system.tmp )
ld86: data segment too large for 16bit
tools/build boot/bootsect boot/setup boot/system > boot/Image
Root device is (3, -128)
Boot sector 512 bytes.
Setup is 1660 bytes.
Unable to open 'system'
make[2]: *** [Image] Error 1
make[2]: Leaving directory `/home/djohanse/elk2/elks/elks/arch/i86'
make[1]: *** [Image] Error 2
make[1]: Leaving directory `/home/djohanse/elk2/elks/elks'
make: *** [elks] Error 2
Build script has terminated with error 4

             reply	other threads:[~2017-03-23  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  3:51 Derek Johansen [this message]
2017-03-24 19:48 ` build.sh errors when enabling kernel hacking -> system trace Alan Cox

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='CAOv0vdncUa_RmHkXKnaN_U=cA+-6kR9dOUm6OY3Oj5t_ucLa1g@mail.gmail.com' \
    --to=djohanse678@gmail.com \
    --cc=linux-8086@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 read-only IMAP folder(s) and NNTP newsgroup(s).