From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harley Laue Subject: Re: Still having a problem building elks kernel Date: Mon, 8 Mar 2010 10:45:39 -0600 Message-ID: References: <4B929115.7070201@gmail.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=RxB3wSZ0RZFnI8cFtdXPzn8HWO+BSrUIQwLbS+WM6vc=; b=iUCT0mrN5tj69gY8LTaI1StSNdN6c9PPyVf3e+WmJXkOX5waszVYk9FzBaucsddGs9 Bqf5GEchGoUgiAgZB44aOYjBOnnufPXmnxczyN0vjXbJVxTSHeADsvNWpwmVg6sRU06Y t1nfeVUewtv4mktVHhYJISbnGBcmMVQgzTczE= In-Reply-To: Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-8086@vger.kernel.org > 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.