#10303: clean up sage-check-64 and use of SAGE64
-----------------------------+----------------------------------------------
Reporter: jhpalmieri | Owner: GeorgSWeber
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-4.6.1
Component: build | Keywords: 64
Author: John Palmieri | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by leif):
Replying to [comment:12 drkirkby]:
> Replying to [comment:10 leif]:
> > Another, safer way to detect if 64-bit builds are supported is to use
`getconf`, e.g.
{{{
#!sh
if [ `getconf _POSIX_V6_LP64_OFF64` -eq 1 ]; then
# 64-bit builds supported
echo "Max. unsigned long: `getconf -v POSIX_V6_LP64_OFF64
ULONG_MAX`"
# should give 2^64-1
fi
}}}
>
> That's not true. Read the section on "Exit Status" on the OpenGroup web
site.
That was just an example. I know one shouldn't test for equality (`-eq
1`), but check that the result (output) is something else than `"-1"` and
`"undefined"`, but that's unrelated to its exit status.
But using `getconf` is safe and IMHO the right direction.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10303#comment:17>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
