John Maddock wrote:

1) Do you have a test case?

I have a mysterious build environment (and a slow workstation that takes a long time to compile template-rich systems). Our leaders hacked the system together to port Makefiles (yes, dumb old Makefiles) transparently between the Linux target and the Win32 development environments. Can't we all just ... get along? This will make extracting a test case that reproduces the environment problematic. Unless you would like me to mail you all of it. ;-)

2) Which STLport version are you using? 3) What compiler runtime are you using?

STLport-4.6.2 Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86 (The IDE is, more familiarily, 7.1) Don't work this until I either get over it or perfect a test case. Or someone else reports something. Either way I'l probably report something to this thread. -- Phlip http://www.greencheese.org/ZeekLand <-- NOT a blog!!

Phlip wrote:

I just reproduced it again. Here's the setup:

$(WIN32_TARGET): export STLPORT_PATH=../STLport-4.6.2/ ;\ export MSVCDir=$VCINSTALLDIR ;\ ./configure --with-toolset=vc-7_1-stlport --with-bjam=tools/build/jam_src/bin.ntx86/bjam.exe ;\ tools/build/jam_src/bin.ntx86/bjam.exe "-sTOOLS=vc-7_1-stlport" --with-regex stage

Then at link time, the application catches:

unresolved external symbol "void __cdecl boost::re_detail::raise_runtime_error(class _STL::runtime_error const &)"...

unresolved external symbol "class _STL::basic_string __cdecl boost::re_detail::w32_transform(unsigned long,char const *,char const *)"...

So I copy and paste those into my application's cpp file, and they link. Then I crash here:

Linker errors are there to tell you something: the lib file you're linking against is *not* binary compatible with your applications build options. So.... are you letting autolink pick the right lib to link against or have you over-riden an error there as well? Are you defining __STL_DEBUG in debug builds? The bjam built libs do so, and you'll need to define __STL_DEBUG to link against them. The autolink code should have picked this one up however. If all esle fails I suggest you build the regex lib from the IDE with *exactly* the same options as your application: remember it's just a bunch of sources, you can add the source code directly to your project as well if you want (define BOOST_REGEX_NO_LIB to disable autolinking if you do so however). Hopefully that will clear the problem's you're seeing. John.