public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
Date: Thu, 23 Feb 2006 16:33:00 -0600	[thread overview]
Message-ID: <200602231633.00470.bss03@volumehost.com> (raw)
In-Reply-To: <200602232256.02982.bo.andresen@gmail.com>

On Thursday 23 February 2006 15:56, Bo Andresen <bo.andresen@gmail.com> 
wrote about 'Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec 
format error':
> > > Will a 64 bit kernel be able to run a 32 bit bash?
> >
> > A 64-bit kernel will run 32-bit binaries fine... Um, there may be a
> > needed kernel option though... CONFIG_IA32_EMUL? Anyone?
>
> I cannot seem to find any such kernel config option.

I think these are relevant:
$ zgrep -i ia32 /proc/config.gz
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y

> > > In order to get a 64
> > > bit kernel a have to set CFLAGS=-march=k8
> >
> > Your CFLAGS in make.conf don't affect your kernel, normally.
>
> Didn't really think so either. It's just that I still get  the Exec
> format error when I try to chroot. Is there a way to very that I really
> am running a 64 kernel?

I believe this tells you:
$ uname -m
x86_64

> > > and set the processor type to
> > > K8 in the kernel configuration, right?
> >
> > Just setting the proper processor type should build your kernel as
> > 64-bit.
>
> Did do that.

The only thing I can't think of at this point is something from the gentoo 
cross compile howto from vapier that may or may not apply:

"If you want to cross compile a kernel, do this:
 make ARCH=hppa CROSS_COMPILE=hppa2.0-unknown-linux-gnu-"

So, you may want to configure, make, and install your kernel like:
make ARCH=x86_64 menuconfig
make ARCH=x86_64
make ARCH=x86_64 install

(You don't need a CROSS_COMPILE prefix since gcc should work fine.)

-- 
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-23 22:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 23:03 [gentoo-user] chroot: cannot run command `bin/bash': Exec format error Bo Andresen
2006-02-22 23:14 ` John Jolet
2006-02-22 23:28   ` [gentoo-user] " Mick
2006-02-22 23:41     ` Bo Andresen
2006-02-22 23:18 ` [gentoo-user] " Boris Fersing
2006-02-22 23:42 ` Boyd Stephen Smith Jr.
2006-02-22 23:51   ` Bo Andresen
2006-02-23 21:31   ` Bo Andresen
2006-02-23 21:40     ` Boyd Stephen Smith Jr.
2006-02-23 21:56       ` Bo Andresen
2006-02-23 22:33         ` Boyd Stephen Smith Jr. [this message]
2006-02-23 23:25           ` Bo Andresen
2006-02-23 23:52             ` Boyd Stephen Smith Jr.
2006-02-24  0:12               ` Bo Andresen
2006-02-24  0:16                 ` Bo Andresen
2006-02-24  0:32                   ` Boyd Stephen Smith Jr.
2006-02-24  0:56                     ` Boyd Stephen Smith Jr.
2006-02-24  1:07                       ` Bo Andresen
2006-02-24  5:18                         ` Boyd Stephen Smith Jr.
2006-02-24 12:56                           ` [gentoo-user] chroot: cannot run command `bin/bash': Exec format error [SOLVED] Bo Andresen
2006-02-24 21:07                             ` Boyd Stephen Smith Jr.

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=200602231633.00470.bss03@volumehost.com \
    --to=bss03@volumehost.com \
    --cc=gentoo-user@lists.gentoo.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