On 4 January 2011 00:22, Volker Braun wrote:
> I don't understand your point. If you have a 64-bit kernel but 32-bit
> userspace then you can't just build a 64-bit Sage. Despite our worst
> attempts we are still not shipping with glibc, ncurses, zlib, freetype, ...
> My system, on the other hand,
> I don't understand your point. If you have a 64-bit kernel but 32-bit
> userspace then you can't just build a 64-bit Sage. Despite our worst
> attempts we are still not shipping with glibc, ncurses, zlib, freetype, ...
>
> My system, on the other hand, is multilib and I think I have all necessar
I don't understand your point. If you have a 64-bit kernel but 32-bit
userspace then you can't just build a 64-bit Sage. Despite our worst
attempts we are still not shipping with glibc, ncurses, zlib, freetype, ...
My system, on the other hand, is multilib and I think I have all necessary
libra
> As far as I know, there is no better way than to look at the binaries (e.g.
> "file $SAGE_LOCAL/bin/python"). That said, I think you are incorrectly
> assuming that SAGE64 corresponds to the architecture. In fact,
>
> SAGE64=yes forces 64-bit build
> SAGE64=no does not force 64-bit, and will
As far as I know, there is no better way than to look at the binaries (e.g.
"file $SAGE_LOCAL/bin/python"). That said, I think you are incorrectly
assuming that SAGE64 corresponds to the architecture. In fact,
SAGE64=yes forces 64-bit build
SAGE64=no does not force 64-bit, and will build what
Thank you, but this has to happen from the bash script "sage", so this
doesn't work. Is there a specific file that would signal it was built
for 64-bit?
Thanks in advance.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sag
I must confess that I don't understand the need for SAGE64. I believe it was
added as a workaround for breakage in the OSX toolchain. But I think the
morally right way to check for what Sage was built with is
sage: import platform
sage: platform.architecture()
('64bit', 'ELF')
which will return
This may be a bit unrelated, but is the SAGE64 flag present on all
platforms, and can it be checked to exist on a binary install? If not,
is there another way to check if Sage was built for 64-bit? I'm asking
this because I'm working on an OS architecture check patch, and this
would require checkin
On 11/22/10 07:55 AM, Peter Jeremy wrote:
On 2010-Nov-20 19:09:00 -0800, John H Palmieri wrote:
Is that the compiler flag "-m64" has no effect on other systems? Some
spkg-install files just check whether SAGE64 is set, not the platform,
and then they add -m64 to the flags. So if that does any
On 2010-Nov-20 19:09:00 -0800, John H Palmieri wrote:
>Is that the compiler flag "-m64" has no effect on other systems? Some
>spkg-install files just check whether SAGE64 is set, not the platform,
>and then they add -m64 to the flags. So if that does anything on
>linux, then SAGE64 can be used o
On 21 November 2010 03:09, John H Palmieri wrote:
> On Nov 20, 5:32 pm, "Dr. David Kirkby"
> wrote:
>> On 11/20/10 10:36 PM, John H Palmieri wrote:
>>
>> > Summarizing, my questions are:
>>
>> > - is SAGE64 supposed to have an effect on platforms other than OS X
>> > and Solaris? (I think so.)
On Nov 20, 5:32 pm, "Dr. David Kirkby"
wrote:
> On 11/20/10 10:36 PM, John H Palmieri wrote:
>
> > Summarizing, my questions are:
>
> > - is SAGE64 supposed to have an effect on platforms other than OS X
> > and Solaris? (I think so.)
>
> I would say yes.
>
> In practice it is only currently us
12 matches
Mail list logo
