[SOLVED] Could not determine MSC version (Visual Studio 2017)

2019-01-27 Thread julien2412
Fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=be887356d94ad813acdf56108ad02fd5e33f803b Thank you Stephan and Mike for your support. Julien -- Sent from: http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html ___

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread julien2412
Kaganski Mike wrote >>... > You could change your VS language to English possibly. And file an issue > to the package upstream. About the issue, I found https://bugzilla.mozilla.org/show_bug.cgi?id=1238154 So now either we can patch locally waiting for a fix on upstream or change VS language. J

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread Kaganski Mike
On 25.01.2019 14:06, julien2412 wrote: > > Now to avoid to patch the package, the idea would be to know why I get > something else than a plain space. Perhaps something to configure on Cygwin > (codepage, LC, ...) > Let's dig on Google... You could change your VS language to English possibly. And

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread julien2412
sberg wrote > ... >> Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27024.1 for x64 >> Copyright (C) Microsoft Corporation. All rights reserved. >> >> cl : Command line warning D9002 : ignoring unknown option '-v' >> cl : Command line error D8003 : missing source filename > > with a true

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread Stephan Bergmann
On 25/01/2019 11:48, julien2412 wrote: Just for curiosity, what's the result for you with the cl commands you provided me? I mean I suppose you must have this non break character too and so sed command should also fail for you, shouldn't it? I get Microsoft (R) C/C++ Optimizing Compiler Versi

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread julien2412
sberg wrote > On 25/01/2019 10:55, julien2412 wrote: >> $ >> C:/PROGRA~2/MIB055~1/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x64/cl.exe >> -v >> Compilateur d'optimisation Microsoft (R) C/C++ version▒19.16.27026.1 pour > > So that character between "version" and "19" (presumably meant to b

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread Stephan Bergmann
On 25/01/2019 10:55, julien2412 wrote: $ C:/PROGRA~2/MIB055~1/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x64/cl.exe -v Compilateur d'optimisation Microsoft (R) C/C++ version▒19.16.27026.1 pour So that character between "version" and "19" (presumably meant to be a no-break space) obviou

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread julien2412
sberg wrote > ... > > In the cygwin shell where you do `make`, do the following: > >> $ grep CC= config_host.mk > to get the CC=... line, should be something like CC=C:/PROGRA... Do the > below two commands, with each XXX replaced by the exact value from that > CC= line: >> $ XXX -v > and > >

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread Stephan Bergmann
On 25/01/2019 09:50, julien2412 wrote: workdir\UnpackedTarball\nss\nspr\out\config.log configure:2543: checking for cl configure:2570: result: cl configure:5898: cl -c conftest.c >&5 conftest.c conftest.c(14): error C2065: '__thumb2__'ÿ: identificateur non d‚clar‚ Compilateur d'optimisation Mi

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-25 Thread julien2412
sberg wrote >>... > From "make[2]: *** [Makefile:129: ../nspr/out/config.status] Error 1" > it looks like this is a failure during configure of external/nss. > workdir/UnpackedTarball/nss/nspr/out/config.log might contain a clue as > to why it fails for you > ... Here's the config.log is "--en

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-24 Thread Stephan Bergmann
On 24/01/2019 21:04, julien2412 wrote: Here what I did to avoid language pb: export LANG=C make clean make Here are the last lines: [build ULF] C:/BLP/libo-core/workdir/ScpMergeTarget/scp2/source/writer/registryitem_writer.ulf [build ULF] C:/BLP/libo-core/workdir/ScpMergeTarget/scp2/source/winex

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-24 Thread julien2412
sberg wrote > On 24/01/2019 15:52, julien2412 wrote: >> I got when using /opt/lo/bin/make >> checking for cl... cl >> configure: error: Could not determine MSC version. > > During the execution of what make target does that failure happen? > Re-execution of LO's top-level configure as triggered b

Re: Could not determine MSC version (Visual Studio 2017)

2019-01-24 Thread Stephan Bergmann
On 24/01/2019 15:52, julien2412 wrote: I got when using /opt/lo/bin/make checking for cl... cl configure: error: Could not determine MSC version. During the execution of what make target does that failure happen? Re-execution of LO's top-level configure as triggered by the makefile, or config

Could not determine MSC version (Visual Studio 2017)

2019-01-24 Thread julien2412
Hello, I'm giving a try with Win build on Win7 with Visual Studio 2017 community retrieved today + master sources. Here's the autogen.sh: --with-system-odbc --with-ant-home=/cygdrive/c/BLP/apache-ant-1.9.5 --with-junit=/cygdrive/c/BLP/junit-4.10.jar --enable-64-bit --enable-werror --enable-debug