Is there not a list for this type of question? A developer's list or
On 08/05/2012 10:46 AM, Tom Davies wrote:
It's probably best to ask on the devs list or theough their iirc (whatever that is!). It's
probably a bit beyond the scope of most people on this list.
It was a good idea to try here first of course bt sometimes all we can do is signpost people to
other places to get better answers.
Apols and regards from
--- On Sun, 5/8/12, firstname.lastname@example.org <email@example.com> wrote:
From: firstname.lastname@example.org <email@example.com>
Subject: [libreoffice-users] Error while building LibreOffice from source code in the configure step
Date: Sunday, 5 August, 2012, 14:01
I got an error while building LibreOffice from source code in the configure step:
$ tar xvf libreoffice-core-184.108.40.206.tar.xz
$ cd libreoffice-core-220.127.116.11
$ ./configure --prefix=/usr
checking which zlib to use... ./configure: line 22518: syntax error near unexpected token `MINIZIP,'
./configure: line 22518: ` libo_MINGW_CHECK_DLL(MINIZIP, libminizip)'
My operating system is a GNU/Linux OS with:
-automake (GNU automake) 1.11.1
-autoconf (GNU Autoconf) 2.68
-libtool (GNU libtool) 2.4
-m4 (GNU M4) 1.4.16
Do you understand why I got this error?
For unsubscribe instructions e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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