From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: linux 2.6.12-rc1-bk5 compilation error
Date: Tue, 05 Apr 2005 09:12:52 +1000 [thread overview]
Message-ID: <1112656372.26086.88.camel@gaston> (raw)
In-Reply-To: <4240b91605040412117b29d4ca@mail.gmail.com>
On Mon, 2005-04-04 at 20:11 +0100, Jerome Glisse wrote:
> > You should really be using a 64 bits kernel :)
>
> Yes, i should, honte à moi :) btw which distribution
> do you use or recommand for 64bits ? gentoo ? I am
> long time debian user (x86) and i think that this is not the
> best choice for ppc64...
I'm using debian 32 bits and do my own 64 bits toolchain for building
kernels ;)
For toolchain, I recommend Janis scripts at penguinppc64.org (toolchain
section, there is a link to mkbiarch etc... I don't use crosstools).
Ben.
next prev parent reply other threads:[~2005-04-04 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 10:32 linux 2.6.12-rc1-bk5 compilation error Jerome Glisse
2005-04-04 10:51 ` Jerome Glisse
2005-04-04 11:52 ` Jerome Glisse
2005-04-04 12:41 ` Benjamin Herrenschmidt
2005-04-04 19:11 ` Jerome Glisse
2005-04-04 23:12 ` Benjamin Herrenschmidt [this message]
2005-04-05 11:52 ` Jerome Glisse
2005-04-05 12:39 ` Andreas Schwab
2005-04-05 15:17 ` Jerome Glisse
2005-04-05 23:12 ` Benjamin Herrenschmidt
2005-04-05 23:25 ` Andreas Schwab
2005-04-05 23:11 ` Benjamin Herrenschmidt
2005-04-07 17:10 ` Tom Rini
2005-04-08 10:13 ` Jerome Glisse
2005-04-08 15:34 ` [PATCH 2.6.12-rc2] ppc32: Fix building 32bit kernel for 64bit machines (Was: Re: linux 2.6.12-rc1-bk5 compilation error) Tom Rini
2005-04-08 22:27 ` Jerome Glisse
2005-04-08 23:47 ` Benjamin Herrenschmidt
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=1112656372.26086.88.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=j.glisse@gmail.com \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.