Hello Vadim,
On 06.12.2013 10:17, Vadim Yedzinovich wrote:
MSVS or SDK was not updated.
good.
I've perform dmake clean:
/cygdrive/c/source/aoo-trunk/main
$ dmake clean
rm -rf */wntmsci12.pro <http://wntmsci12.pro>
rm -rf solver/*/wntmsci12.pro <http://wntmsci12.pro>
rm -rf ../ext_libraries/*/wntmsci12.pro <http://wntmsci12.pro>
echo cleaning up dmake...
cleaning up dmake...
make -C dmake clean
make: *** dmake: No such file or directory. Stop.
As recommend here: http://www.openoffice.org/tools/troubleshoot.html
<http://www.openoffice.org/tools/troubleshoot.html>
Not sure if it is corresponding to 'clean build' that your recommend to
do...
That's as clean as it gets ;-)
Then get the latest version with SVN:
svn info
Better use "svn update" for updating, but for finding out what actual
AOO version you got use "svn info|grep Rev:".
Pefrorm build instructions from step: Run autoconf to create the
configure script:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7
Start: Build --all
and have just the same problem with
C:\...oft Visual Studio 9.0\VC\include>xhash
So probably I still have old headers files somewhere around ...
Sorry, but I dont know what I need to do with MSVC's bitset header to
have correct definition for _STL namespace...
I'm afraid we have to check the preprocessed output of the problematic
source file. Please find out how this file is compiled in your
environment by cd'ing into the sal module directory and then run
build verbose=1 | grep debugbase.cxx
there. This will tell you the compiler command line for debugbase.cxx.
Use this command line, but modify it using [1] to make the compilation
stop after the preprocessor step. In short: you probably have to replace
the -c option with the -E or the -P option.
[1]
http://stackoverflow.com/questions/8978997/how-can-i-see-the-output-of-the-visual-c-preprocessor
Then look into the output of preprocessor and search in which namespace
and where basic_string gets defined. Then look where the _STL define
gets into the play and why it is expected later from the xhash header.
This should help to find the root cause of the problem.
Hope that helps,
Herbert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
