Intel 7.1-linux tarball results
Martin, Almost all Intel 7.1 tarball tests fail with the following diagnostics (from http://tinyurl.com/4jvoo): /opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0x29): In function `_Getctyptab': : undefined reference to `__ctype_b' /opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0x41): In function `_Getctyptab': : undefined reference to `__ctype_b' /opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0x66): In function `_Getctyptab': : undefined reference to `__ctype_b' /opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0x8b): In function `_Getctyptab': : undefined reference to `__ctype_b' /opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0xb0): In function `_Getctyptab': : undefined reference to `__ctype_b' /opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0xd2): more undefined references to `__ctype_b' follow . /opt/intel/compiler70/ia32/bin/iccvars.sh icpc -g -o "../bin/boost/libs/algorithm/minmax/test/minmax.test/intel-7.1-linux/debug/minmax" "../bin/boost/libs/algorithm/minmax/test/minmax.test/intel-7.1-linux/debug/minmax_test.o" -lrt This is obviously a configuration/environment problem, but it'd be nice to get the reports cleaned from all these red cells. Could you take a look into this, please? -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Almost all Intel 7.1 tarball tests fail with the following diagnostics (from http://tinyurl.com/4jvoo):
/opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0xb0): In function `_Getctyptab': : undefined reference to `__ctype_b'
This is obviously a configuration/environment problem, but it'd be nice to get the reports cleaned from all these red cells. Could you take a look into this, please?
I cleared the the results for intel 7.1 and I'm currently rerunning the tests. However, I already can say the problem persists. I'm afraid this could be caused by an update to the libc on my box. Some of the intel libraries explicitely refer to __ctype_b@@GLIBC_2.0 However, on my box there's only GLIBC_2.3 stuff. I don't know how to proceed. Regards, m
Martin Wille writes:
Aleksey Gurtovoy wrote:
Almost all Intel 7.1 tarball tests fail with the following diagnostics (from http://tinyurl.com/4jvoo):
/opt/intel/compiler70/ia32/lib/libcprts.a(xlocinfo.o)(.text+0xb0): In function `_Getctyptab': : undefined reference to `__ctype_b'
This is obviously a configuration/environment problem, but it'd be nice to get the reports cleaned from all these red cells. Could you take a look into this, please?
I cleared the the results for intel 7.1 and I'm currently rerunning the tests. However, I already can say the problem persists.
I'm afraid this could be caused by an update to the libc on my box. Some of the intel libraries explicitely refer to __ctype_b@@GLIBC_2.0 However, on my box there's only GLIBC_2.3 stuff.
That's a pity. But I'd say if we cannot fix it, it'd be less misleading if we took the configuration out of the tests. May be somebody else can test Intel 7.1 on Linux? -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Martin Wille writes:
[...]
I'm afraid this could be caused by an update to the libc on my box. Some of the intel libraries explicitely refer to __ctype_b@@GLIBC_2.0 However, on my box there's only GLIBC_2.3 stuff.
(I tried to install glibc 2.0.6 in the meantime. However, that failed miserably due to syntax errors. Interestingly, glibc 2.0.6. recommends gcc 2.7.2.3 which I outright refuse to install.)
That's a pity.
Indeed. But I'd say if we cannot fix it, it'd be less misleading
if we took the configuration out of the tests.
I agree. I'll remove intel-7.1 from my set of toolsets. May be somebody else
can test Intel 7.1 on Linux?
I start to doubt it'd make sense to support 7.1 after the 1.32 release. If the compiler requires such ancient stuff then it will get abandoned quickly by developers. Regards, m
participants (2)
-
Aleksey Gurtovoy -
Martin Wille