On 1/11/2010 2:28 PM, Herman Schultz wrote:
> I tried configure --with-stlport=<path> but that didn't seem to have any
Where do you see it documented that it should?
> My problem is an unresolved symbol error in one our apps:
> undefined reference to
> stlp_std::char_traits<char>, stlp_std::allocator<char> > const&,
> Looks a mixing of stl and stlport to me.
To make your compiler find the STLport headers before its standard C++
library, something this should work:
$ ./configure CXXFLAGS=-I/where/stlport/is --other-flags
This is off the cuff, because I haven't used STLport since the days when
most compiler vendors shipped broken STL implementations, or didn't ship
STL at all. Why would one use STLport today?