Hi
Sometime in the last 24 hours something changed in the mozilla configure stuff, which means that
autogen is failing for
me now.
Running on a Windows7 machine with Visual Studio.
See attached log.
Anybody have any ideas?
Thanks, Noel Grandin
Disclaimer: http://www.peralex.com/disclaimer.html
./autogen.sh
running ./configure with '--with-max-jobs=9' '--with-num-cpus=2' '--without-junit'
'--with-ant-home=/cygdrive/c/Components/apache-ant-1.8.0' '--disable-build-mozilla' '--disable-atl'
'--disable-activex' '--disable-nss-module' '--without-java' '--disable-mozilla'
configure: WARNING: unrecognized options: --disable-nss-module
********************************************************************
*
* Running LibreOffice build configuration.
*
********************************************************************
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for gawk... gawk
checking for gawk... /usr/bin/gawk
checking for sed... /usr/bin/sed
checking for bash... /usr/bin/sh
checking for GNU or BSD tar... tar
checking for Cygwin gcc/g++... found
checking for ccache... not found
checking gcc home... /usr
checking whether to enable crashdump feature... no
checking whether to build a 64-bit LibreOffice... no
checking whether to use DirectX... yes
checking whether to use ActiveX... no
checking whether to use ATL... no
checking whether to turn warnings to errors... no
checking whether to do a debug build... no
checking whether to build with additional debug utilities... no, full product build
checking whether to use linkoo for the smoketest installation... yes
checking whether to use link-time optimization... no
checking whether to include symbols... no
checking whether to strip the solver or not.... yes
checking whether we need fontconfig... no
checking whether to enable filters for legacy binary file formats (StarOffice 5.2)... no
checking whether to build help... yes
checking whether to use RPATH in shared libraries... yes
checking whether to include MySpell dictionaries... yes
checking whether to use dicts from external paths... no
checking whether to enable pch feature... no
checking for GNU make... /opt/lo/bin/make
checking the GNU make version... /opt/lo/bin/make 3.82
checking for --hash-style gcc linker support ... no
checking for perl... /usr/bin/perl
checking the Perl version... checked (perl 5)
checking for required Perl modules... all modules found
checking for a friendly Microsoft C/C++ compiler installation path...
/cygdrive/c/PROGRA~1/MICROS~1.0/VC
checking the Microsoft C/C++ Compiler... found (/cygdrive/c/PROGRA~1/MICROS~1.0/VC/bin/cl.exe)
checking the Version of Microsoft C/C++ Compiler... found compiler version 001500003072 (MSVS 2008).
checking the dependency generation prefix (cl.exe -showIncludes)... "Note: including file:"
checking for a x64 compiler and libraries for 64bit ActiveX component... not found
configure: WARNING: Installation set will not contain the 64-bit Explorer extension
checking for midl.exe... no
checking for csc.exe... no
checking .NET Framework... found
checking valgrind.h usability... no
checking valgrind.h presence... no
checking for valgrind.h... no
checking valgrind.h usability... no
checking valgrind.h presence... no
checking for valgrind.h... no
checking Whether building STLPort library makes sense... yes
checking Whether STLPort library will be actually built... yes
checking whether /cygdrive/c/PROGRA~1/MICROS~1.0/VC/bin/cl.exe supports thread safe statics...
unknown (assuming no)
checking which memory allocator to use... internal
checking whether to add custom build version... no
checking whether to build with Java support... no
checking for dmake... no
dmake will be built on ./bootstrap
checking whether to enable EPM for packing... no
checking for gperf... /usr/bin/gperf
checking gperf version... OK
checking whether to build the stax... checking whether to build the ODK... yes
checking whether to provide libstdc++/libgcc_s in the installset... yes
checking which zlib to use... internal
checking which jpeg to use... internal
checking which expat to use... internal
checking which libvisio to use... internal
checking which libcmis to use... internal
checking which libwpd to use... internal
checking which cppunit to use... internal
checking which libwps to use... internal
checking which libwpg to use... internal
checking which libxslt to use... internal
checking which libxml to use... internal
checking which Python to use... internal
checking for bzip2... /usr/bin/bzip2
checking which db to use... internal
checking whether to build the MySQL Connector extension... no
checking which libcurl to use... internal
checking which boost to use... internal
checking which mdds to use... internal
checking which hash container mdds shall use... boost::unordered_map
checking which vigra to use... internal
checking which odbc headers to use... internal
checking whether to enable build of Mozilla... no
checking whether to build Mozilla addressbook connectivity... no
checking whether to build XML Security support... yes
checking whether to build LDAP configuration backend... no. Either Mozilla or OpenLDAP needed
checking which Mozilla to use... none
checking which NSS to use... internal
checking for Mozilla build tooling... configure: error: Mozilla build tooling not found.
Use the --with-mozilla-build option after installing the tools obtained
from http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32
Error running configure at ./autogen.sh line 157.
make: *** [Makefile] Error 2
Context
- [Libreoffice] build breaking in configure · Noel Grandin
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.