linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sourceforge.net>
To: linuxppc-dev@lists.linuxppc.org
Cc: benh@kernel.crashing.org
Subject: Re: 64-bit user-space on G5? Never, soonish, or unknown?
Date: 28 Feb 2004 18:16:28 -0500	[thread overview]
Message-ID: <1078010187.2233.105.camel@cube> (raw)


Benjamin Herrenschmidt writes:

> The 64 bits kernel allow you to run both 32 and
> 64 bits userland, the common practice is to have
> a 32 bit userland with the necessary libs to be
> able to build & run _some_ 64 bits executables.

You'd better have a 64-bit ncurses. If you don't,
your procps will be compiled incorrectly. Data
will get truncated, mangled, etc. -- assuming you
can even run the tools at all.

The same goes for pretty much any other lib.
If it isn't a package-private lib, you need
it in a 64-bit version. The 32-bit libs can
go in an optional compatibility package.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-02-28 23:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 23:16 Albert Cahalan [this message]
2004-03-01 22:38 ` 64-bit user-space on G5? Never, soonish, or unknown? linas
2004-03-01 23:42   ` Albert Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2004-02-12  7:49 Mikael Pettersson
2004-02-12  7:47 Mikael Pettersson
2004-02-11 14:09 Mikael Pettersson
2004-02-11 14:51 ` Christian Kujau
2004-02-11 15:33 ` tom_gall
2004-02-11 22:14 ` Benjamin Herrenschmidt
2004-02-11 22:26 ` Anton Blanchard

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=1078010187.2233.105.camel@cube \
    --to=albert@users.sourceforge.net \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.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).