On 11.07.19 20:38, Oliver Brinzing wrote:
Hi,
are there any known building issues at the moment?
my windows x64 master build with VS 2017 15.9.12  stops reproducible at: 
[MOD] scp2
there is no error message...
a full build after clean did not help.
there was some discussion yesterday but no solution:
<tml_> anybody else noticed that a Windows build (Windows 10) now seems to hang somewhere?
<mikekaganski> tml_: yes, in running cl -?
<mikekaganski> tml_: it was in building ODK for me
<tml_> hmm, yes, I see a cl process there
<mikekaganski> just killing it continues ... something strange
<mikekaganski> tml_: looks like cl.exe possibly started to wait for user input when used with -? 
switch
<tml_> I use --disable-odk though
* mikekaganski haven't yet had a chance to debug
<tml_> killed the cl and now it proceeds
* mikekaganski had to do that twice or thrice
are you seeing the same symptoms?
Regards
Oliver
cd /cygdrive/d/sources/libo-core
./g checkout master
./g fetch --tags
./g pull -r
/opt/lo/bin/make build-nocheck gb_COLOR=1 gb_TITLES=1 2>&1 | tee build.log
/cygdrive/d/sources/libo-core/autogen.sh \
         --with-external-tar=/cygdrive/d/sources/lo-externalsrc \
         --with-junit=/cygdrive/d/sources/junit-4.10.jar \
         --with-ant-home=/cygdrive/d/sources/apache-ant-1.9.5 \
         --with-jdk-home=/cygdrive/d/Programme/Java/jdk1.8.0x64 \
         --enable-pch --disable-ccache --enable-debug --enable-64-bit 
--disable-odk
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.