public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Harley Laue <losinggeneration@gmail.com>
To: linux-8086@vger.kernel.org
Subject: Re: Still having a problem building elks kernel
Date: Mon, 8 Mar 2010 10:45:39 -0600	[thread overview]
Message-ID: <ef8d4e9b1003080845g4df26837o3b20b69380d79f34@mail.gmail.com> (raw)
In-Reply-To: <ba3128e11003080817p32ea3090k2fa0b6650ff2caf6@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?

Oh, I think I know what the issue may be. I just tested building Elks in a 32
bit Ubuntu chroot (much quicker then a VM.) It seems something that there
are assumptions that the environment is 32 bit. I'd guess it's probably
./arch/i86/tools/build.c that's making assumptions someplace it shouldn't
about the size of int, char, long, etc. For now I guess setup a 32 bit system
(VM or chroot should both work fine), or if you're feeling ambitious, you can
try tackling the issue in that's probably in the file I mentioned.

  parent reply	other threads:[~2010-03-08 16:45 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
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     ` Harley Laue [this message]
2010-03-08 16:50       ` Still having a problem building elks kernel 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=ef8d4e9b1003080845g4df26837o3b20b69380d79f34@mail.gmail.com \
    --to=losinggeneration@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