--enable-pch makes it use precompiled headers. The error messages are
quite clear.
Now you have to run
make clean
and then build again.
Ilmari
anshu khare kirjoitti 4.7.2020 klo 22.20:
I ran autogen.sh as shown below :
/cygdrive/c/sources/libo-core/autogen.sh
--with-external-tar=/cygdrive/c/sources/lo-externalsrc
--with-junit=/cygdrive/c/sources/junit-4.10.jar
--with-ant-home=/cygdrive/c/sources/apache-ant-1.9.5
--enable-pch --disable-ccache
--enable-64-bit
--disable-skia
--with-jdk-home=/cygdrive/c/ProgramFiles/Java/jdk-13.0.2
It gave the following output :
Host Configuration unchanged - avoiding scp2 stamp update
Language Configuration unchanged - avoiding scp2 stamp update
****************************************************************************
To build, run:
C:/cygwin64/opt/lo/bin/make
To view some help, run:
C:/cygwin64/opt/lo/bin/make help
Then I ran the following command :
/opt/lo/bin/make gb_COLOR=1
as given in the documentation.
I got the following output :
C:/sources/libo-core/sal/osl/all/filepath.cxx: fatal error C1853:
'C:/build/workdir/PrecompiledHeader/nodebug/precompiled_sal.hxx.pch'
precompiled header file is from a different version of th
e compiler, or the precompiled header is C++ and you are using it from C
(or vice versa)
C:/sources/libo-core/sal/osl/all/loadmodulerelative.cxx: fatal error
C1853:
'C:/build/workdir/PrecompiledHeader/nodebug/precompiled_sal.hxx.pch'
precompiled header file is from a different ver
sion of the compiler, or the precompiled header is C++ and you are using
it from C (or vice versa)C:/sources/libo-core/sal/osl/all/debugbase.cxx:
fatal error C1853: 'C:/build/workdir/Precompil
edHeader/nodebug/precompiled_sal.hxx.pch' precompiled header file is
from a different version of the compiler, or the precompiled header is
C++ and you are using it from C (or vice versa)
C:/sources/libo-core/sal/osl/all/compat.cxx: fatal error C1853:
'C:/build/workdir/PrecompiledHeader/nodebug/precompiled_sal.hxx.pch'
precompiled header file is from a different version of the
compiler, or the precompiled header is C++ and you are using it from C
(or vice versa)
make[1]: *** [C:/sources/libo-core/solenv/gbuild/LinkTarget.mk:301:
C:/build/workdir/CxxObject/sal/osl/all/filepath.o] Error 2
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [C:/sources/libo-core/solenv/gbuild/LinkTarget.mk:301:
C:/build/workdir/CxxObject/sal/osl/all/loadmodulerelative.o] Error 2
make[1]: *** [C:/sources/libo-core/solenv/gbuild/LinkTarget.mk:301:
C:/build/workdir/CxxObject/sal/osl/all/debugbase.o] Error 2
make[1]: *** [C:/sources/libo-core/solenv/gbuild/LinkTarget.mk:301:
C:/build/workdir/CxxObject/sal/osl/all/compat.o] Error 2
make: *** [Makefile:282: build] Error 2
On Sat, Jul 4, 2020 at 11:52 PM Jan-Marek Glogowski <glogow@fbihome.de
<mailto:glogow@fbihome.de>> wrote:
Am 04.07.20 um 18:16 schrieb anshu khare:
> C:\PROGRA~1\Java\JDK-13~1.2\lib\jawt.lib : warning LNK4272:
library
> machine type 'x64' conflicts with target machine type 'x86'
Quote: "Make sure to get a 32-bit SDK if you are building for 32-bit
Windows, and a 64-bit SDK if you are building for 64-bit Windows
(with
--enable-64-bit).
You can use --with-jdk-home=/cygdrive/c/Program
Files/Java/jdk-14.0.1 to
select the correct one.
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
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.