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 18:56:45 -0600	[thread overview]
Message-ID: <200602231856.45372.bss03@volumehost.com> (raw)
In-Reply-To: <200602231832.13268.bss03@volumehost.com>

On Thursday 23 February 2006 18:32, "Boyd Stephen Smith Jr." 
<bss03@volumehost.com> wrote about 'Re: [gentoo-user] chroot: cannot run 
command `bin/bash': Exec format error':
> Try:
> make ARCH=x86_64 CFLAGS=-m64

Nah, don't.  It won't help, the kernel's Makefile doesn't pay attention to 
CFLAGS, it sets up it's own based on your .config.

While I didn't get the same error as you, I see definite "I'm trying to 
compile 64-bit assembly into 32-bit binaries"-style errors when compiling 
with:
make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu-
make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CFLAGS="-m32"
make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CFLAGS="-m64"
and
make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CC="gcc -m32"

However, I /was/ able to convince the kernel to build with
make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CC="gcc -m64"
although I didn't see if that would boot.

So, why don't you give it a go with:
make ARCH=x86_64 CC="gcc -m64" menuconfig
make ARCH=x86_64 CC="gcc -m64"
make ARCH=x86_64 CC="gcc -m64" modules_install
make ARCH=x86_64 CC="gcc -m64" install

and let me know how it goes.

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



  reply	other threads:[~2006-02-24  1:01 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.
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. [this message]
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=200602231856.45372.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