Am 15.09.11, 17:50 -0700 schrieb Jeremy Selan:

*everywhere*? For example, at SPI we have a vm with an old libstdc++
for compatibility testing. Core OCIO builds fine on this machine, but
littlecms has linking issues. (below).

[ 48%] Building CXX object
src/core/CMakeFiles/OpenColorIO.dir/Transform.cpp.o
.libs/cmserr.o: In function `feof_unlocked':
/usr/include/bits/stdio.h:123: multiple definition of `feof_unlocked'
.libs/cmscnvrt.o:/usr/include/bits/stdio.h:123: first defined here
.libs/cmserr.o: In function `ferror_unlocked':

That looks like cmake output. But littleCMS (alias lcms) uses autotools and is written in C not C++. Did you check with lcms' native build system?
Btw. the functions above are not present inside lcms' code. Usually lcms runs on a wide scale of systems, from embedded to many flawours of desktop systems. I would be astonished if there where unresolvable or even hard portability problems.

kind regards
Kai-Uwe Behrmann
--
developing for colour management www.behrmann.name + www.oyranos.org