David Abrahams writes:
Martin Wille <mw8329@yahoo.com.au> writes:
There is no file named "libstlport_gcc_stldebug_static.a" here. Instead, there is "libstlport_gcc_stldebug.a". Is the library name being generated incorrectly, or would the additional "static" in the library name indicate something different than what the ".a" indicates in contrast to the ".so" extension used by shared libraries?
The last four lines of tools/build/v1/stlport.jam show the relationship between build properties and the name of the stlport library being loaded. If the name is wrong, either it was always wrong, or STLPort changed the names of the libraries they build.
Should be fixed in the CVS now. Martin, just in case, could you please remove the binaries for "gcc-2.95.3-stlport-4.5.3-linux" to force bjam to recognize the change? -- Aleksey Gurtovoy MetaCommunications Engineering