Summary: | openssl-0.9.7e abnormal when using ppc32 on a ppc64 cpu | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kraml Liu <kraml.liu> |
Component: | [OLD] Library | Assignee: | ppc64 architecture team <ppc64> |
Status: | VERIFIED INVALID | ||
Severity: | major | CC: | aliz, vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kraml Liu
2005-01-26 08:11:26 UTC
what does `uname -a` and `uname -m` show ? ive changed the ppc64 patch back to only apply when $ARCH == ppc64, but this is really wrong behavior ... when running 32bit x86 inside of 64bit x86_64, `uname -m` dumps 'i686' instead of 'x86_64' ... i imagine that a ppc64 should show the same behavior if your userland is pure 32bit uname -a and -m shows it's ppc64. my kernel was compiled under ppc64 toolchain, it's a 64bit one. The userland is pure 32bit. emerge sync'ed and the problem is gone. thanks! good news.. marking as INVALID. closing |