public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Dieter Kedrowitsch <dieter.kedrowitsch@gmail.com>
To: linux-8086@vger.kernel.org
Subject: Re: Still having a problem building elks kernel
Date: Mon, 8 Mar 2010 11:17:08 -0500	[thread overview]
Message-ID: <ba3128e11003080817p32ea3090k2fa0b6650ff2caf6@mail.gmail.com> (raw)
In-Reply-To: <ef8d4e9b1003051347v7f838265qead71a6c6ee77ece@mail.gmail.com>

I just created a new VM and installed Arch Linux last night.  I'll try
installing the bcc x86 packages this evening and cross my fingers that
this distro does the trick.  I wonder what the difference is?


On Fri, Mar 5, 2010 at 4:47 PM, Harley Laue <losinggeneration@gmail.com> wrote:
> Sorry, I meant to get back to you sooner. I run into the exact same
> thing with Debian, but not Arch Linux.
> Here's the last little bit from Make on Arch which seems to work (I
> don't have the means to actually test it though)
>
> as86 -0  -o boot/crt0.o boot/crt0.s
> (cd ../.. ; ld86 -0 -i   \
>                -t -M -o arch/i86/boot/system \
>                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 \
>                > System.tmp ; \
>                sort -k4 System.tmp > System.map ; rm -f System.tmp )
> tools/build boot/bootsect boot/setup boot/system > boot/Image
> Root device is (3, -128)
> Boot sector 512 bytes.
> Setup is 1596 bytes.
> System is 117788 B (58784 B code, 7728 B data and 51276 B bss)
> System is 66544
> make[2]: Leaving directory `/home/harley/Source/elks-project/elks/arch/i86'
>
>
> Obviously the ld86 is failing in Debian/Ubuntu, but like I said, I
> haven't looked into why yet other then the fact that it looks like "-t
> -M -o arch/i86/boot/system \" isn't in the Debian/Ubuntu's ld86's
> command for some reason...
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-03-08 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 17:29 Still having a problem building elks kernel Dieter R Kedrowitsch
2010-03-05 21:47 ` Harley Laue
2010-03-05 21:57   ` Harley Laue
2010-03-08 16:17   ` Dieter Kedrowitsch [this message]
2010-03-08 16:43     ` Hans
2010-03-09 17:54       ` Still having a problem building elks kernel (nospam: message 15 of 20) Dieter Kedrowitsch
2010-03-10  8:41         ` Hans
2010-03-08 16:45     ` Still having a problem building elks kernel Harley Laue
2010-03-08 16:50       ` Dieter Kedrowitsch
2010-03-09 15:41       ` Still having a problem building elks kernel (nospam: message 16 of 20) Dieter Kedrowitsch

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=ba3128e11003080817p32ea3090k2fa0b6650ff2caf6@mail.gmail.com \
    --to=dieter.kedrowitsch@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