Frans de Boer wrote:
There is however a warning displayed:
....
++ INTMAX_MIN=-9223372036854775808
++ INTMAX_UFLOW=-9223372036854775809
++ UINTMAX_MAX=18446744073709551615
++ UINTMAX_OFLOW=18446744073709551616
++ FLT_MIN=1.1754944e-38
++ FLT_MAX=3.4028235e+38
++ DBL_MIN=2.2250738585072014e-308
++ DBL_MAX=1.7976931348623157e+308
++ LDBL_MIN=3.3621031431120935063e-4932
++ LDBL_MAX=1.189731495357231765e+4932
+ test 2147483647
+ cat
+ skip_ 'this test runs only on systems with glibc and long double !=
double'
@Bruce: your system shows the limit for a 32-bit system, might be the
reason why it works with your system?
Well I have:
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 12
On-line CPU(s) list: 0-11
Model name: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
Generally an int is defined as 32-bits, even on a 64-bit system. To
change from that, you need to specify short int or long int or long long
int to change that, even on non-32 bit systems.
What does your version of /usr/include/limits.h say?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
