Boost Testing :
From: Robert Ramey (ramey_at_[hidden])
Date: 2004-11-16 13:17:53
Isn't this a link from the 1.32 release package. Can't the link just be
left and point to the updated results? In fact, isn't possible that a newer
version of a compiler (e.g. gcc 3.4.3?) comes out and we want to re-run show
updated test results eventhough the 1.32 package is frozen. I don't see
this has having anything to do with release drafts.
"Aleksey Gurtovoy" <agurtovoy_at_[hidden]> wrote in message
> 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
> > > : undefined reference to `__ctype_b'
> > > This is obviously a configuration/environment problem, but it'd be
> > > 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