64-bit user-space on G5? Never, soonish, or unknown?
Quoted 4 lines · Benjamin Herrenschmidt
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/
Hi Albert,
Quoted 8 lines · Albert Cahalan
Quoted 4 lines · Benjamin Herrenschmidt
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.
Quoted 4 lines
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.
? My ps, top, w all work fine:
linas@panic:~> file /usr/bin/top/usr/bin/top: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), stripped linas@panic:~> file /bin/ps/bin/ps: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), stripped
They've been running fine, with all manner of mangled and hacked 2.4 and 2.6 kernels.
--linas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 9 lines · On Mon, 2004-03-01 at 17:38, [email protected] wrote:
Quoted 4 lines · Albert Cahalan
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.
? My ps, top, w all work fine:
Quoted 7 lines
linas@panic:~> file
/usr/bin/top/usr/bin/top: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), stripped linas@panic:~> file/bin/ps/bin/ps: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), strippedThey've been running fine, with all manner of mangled and hacked 2.4 and 2.6 kernels.
Try this:
ps -eo drs,trs,tsiz,dsiz,start_stack,esp,eip,nwchan,wchan
(especially when examining a 64-bit process or when running on the 2.4 kernel)
By "assuming you can run the tools at all" I mean that you might end up with 32-bit libraries in /lib64. If you build on a pure 32-bit system this won't happen.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/