linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Koschmann - GKT <gktnews@gktech.net>
To: Andi Kleen <ak@muc.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: amd64 questions
Date: Wed, 7 Apr 2004 10:36:05 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.30.0404071015000.17695-100000@penguin.gktech.net> (raw)
In-Reply-To: <m3zn9o58n0.fsf@averell.firstfloor.org>

On Wed, 7 Apr 2004, Andi Kleen wrote:
> Debian seems to have some unique problems in the way they handle AMD64
> compared to other distributions. I would not trust what you read
> there, they make it much more complicated than it really is. The right
> forum would have been discuss@x86-64.org

I was hoping that was the case. I wouldn't think the only way would be so
"rigged". I will check out the x86-64 list, thanks for that.

> It's that way. You just need a 64bit capable cross compiler to compile
> the kernel, which is not that difficult to build from sources. You can also
> find binaries for that at
> ftp://ftp.suse.com/pub/suse/x86_64/supplementary/CrossTools/8.1-i386/
> (usable with rpm2cpio on non RPM distributions). Then you can
> cross compile the kernel in the normal way with
> make ARCH=x86_64 CROSS_COMPILE=x86_64-linux-

Great, much better than I had hoped. I always build from source, I'm
guessing I can find something on freshmeat.

> A few programs (namely iptables and ipsec tools) need to be used
> as 64bit programs because the 32bit emulation doesn't work for them.
> ipchains works though.

Okay, thanks for the tip, that probably would have gotten me when I
started installing.

Thanks for all the information Andi, it was extremely helpful!

	Bryan


  parent reply	other threads:[~2004-04-07 17:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1I8up-46J-3@gated-at.bofh.it>
2004-04-07 11:29 ` amd64 questions Andi Kleen
2004-04-07 15:24   ` Paul Wagland
2004-04-07 17:36   ` Bryan Koschmann - GKT [this message]
     [not found] <1Ijzw-4ff-5@gated-at.bofh.it>
     [not found] ` <1Ijzv-4ff-3@gated-at.bofh.it>
     [not found]   ` <1IntE-7wn-39@gated-at.bofh.it>
2004-04-07 16:15     ` Andi Kleen
2004-04-07 16:49       ` Chris Friesen
2004-04-07 18:08         ` Andi Kleen
2004-04-10 16:54       ` J. Ryan Earl
2004-04-10 18:49         ` Andi Kleen
2004-04-10 19:02           ` Hugo Mills
2004-04-11 11:37             ` Paul Wagland
2004-04-11 11:45               ` Hugo Mills
2004-04-10 20:01           ` J. Ryan Earl
2004-04-06 23:37 Bryan Koschmann - GKT

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=Pine.LNX.4.30.0404071015000.17695-100000@penguin.gktech.net \
    --to=gktnews@gktech.net \
    --cc=ak@muc.de \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).