On 07/23/2012 11:53 PM, Keshav Kini wrote:
tvn<[email protected]> writes:
That's what I mean: my Debian OS is *NOT* 64 bit -- uname -a *DOES
NOT* tell you about the OS but rather the capability of the machine
hardware. If the build script makes the same assumption and attempts
to build 64 bit packages based on uname's out then this should be a
bug -- as shown in my situation.
`uname` output tells you about the target architecture the kernel was
built for, not the capability of the machine hardware. It looks to me
like you're running a 32-bit userland on top of a 64-bit kernel (from
what little I know of such things). That is an unusual situation afaik
and I wouldn't be surprised if Sage is buggy on such systems...
-Keshav
+1
I think you are right. The kernel is 64bit but the userland is 32bit. I
just now tested sysresccd with 64bit kernel in a virtualbox and the
setup is similar to tvn's. gcc output gives 32bit executables.
This is indeed an unusual setup.
On the other hand a 32bit kernel + 32bit userland shows up as i686 in
uname -a (in virtualbox).
--
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
