On Thu, Sep 30, 2010 at 07:18:13PM +0200, Thomas Klausner wrote:
While doing that, I found the following issues:
1) automake-1.11.1 complains a lot about GNU make extensions in
Makefile.am files:
bin/piece/Makefile.am:1: wildcard env-*: non-POSIX variable name
bin/piece/Makefile.am:1: (probably a GNU make extension)
[...]
That one's still open. No suggestions? Or just ignore for now?
7) patches/apply.pl is unhappy about the version number returned by
NetBSD's patch:
Patch version 2.0-12u8-NetBSD
Use of uninitialized value $ver_line in pattern match (m//) at
/archive/cvs/libreoffice/build/patches/apply.pl line 924.
Can't get patch version
Usually, NetBSD patch works fine, do we want to force GNU patch or
should I change it to accept NetBSD's patch as well?
The problem here was that NetBSD patch reports version to stderr. I've
fixed that on both sides: LO now looks at stderr as well, and
NetBSD-6.0's patch will report version to stdout.
New open issues:
8) /archive/cvs/libreoffice/build/bin/transform: /archive/cvs/libreoffice/build/bin/font-munge: not
found
The problem here is that the this script wants to run /usr/bin/perl,
but with arguments:
#!/usr/bin/perl -pi.bak -w
Replacing it with /usr/bin/env doesn't work since then we can't
provide further command line arguments in that case.
The Makefile in that directory already contains a perfectly usable
${PERL} variable; then we'd need to
git mv font-munge font-munge.in
and add a rule
font-munge: font-munge.in
sed "s,/usr/bin/perl,${PERL},g" font-munge.in > font-munge
chmod 555 font-munge
to the Makefile. That would work, except I don't know on which target
to hang the dependency so that font-munge is created early enough.
Suggestions?
And I'm stuck at the next point:
9) I run "./autogen.sh --with-distro=LibreOfficeLinux --with-git
--with-max-jobs=16 --with-num-cpus=8" and then gmake (GNU make) and
configure dies with:
********************************************************************
* *
* OpenOffice.org build configuration. *
* *
* The configure process checks your platform to see whether *
* you can build OpenOffice.org on it. *
* This process checks all pre-requisites and generates a file *
* containing the necessary environment variables. *
* Source this file after configure has ended successfully. *
* *
* Any warning that is generated during the configure process *
* must be taken into account since it can be a reason for *
* an unsuccessful build of OpenOffice.org *
* *
********************************************************************
********************************************************************
* *
* Checking the platform pre-requisites. *
* *
********************************************************************
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking for awk... /usr/bin/awk
checking for sed... /usr/bin/sed
checking for solenv environment... default
checking build system type... Invalid configuration `3.2.99.1': machine `3.2.99.1' not recognized
configure: error: /bin/bash ./config.sub 3.2.99.1 failed
gmake: *** [stamp/build] Error 1
The problem here are the configure arguments. According to config log:
head -20 build/libreoffice-3.2.99.1/config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.68. Invocation command line was
$ ./configure --disable-binfilter --disable-crashdump --with-lang= --with-use-shell=bash
--without-gpc --without-agg --disable-fetch-external --with-vba-package-format=builtin
--disable-epm --with-openldap --with-build-version=libreoffice-build 3.2.99.1 --without-fonts
--with-system-jpeg --with-system-libxml --with-system-mozilla --with-system-openssl
--with-system-python --with-system-stdlibs --with-system-zlib --with-system-poppler
--with-unix-wrapper=ooffice3.3 --enable-evolution2 --enable-dbus --with-alloc=system
--enable-cairo=yes --enable-gtk --enable-kde --enable-kde4 --with-vendor=The Document Foundation
--disable-dbus --disable-kde4 --disable-access --enable-cairo --without-system-cairo
--enable-gstreamer --enable-odk --enable-binfilter --enable-gnome-vfs --enable-hids
--enable-lockdown --enable-opengl --enable-ogltrans --with-java-target-version=1.5 --with-jdk-home=
--without-myspell-dicts --enable-epm --enable-kde --without-system-mozilla
--without-system-freetype --without-system-jpeg --without-system-libxml --without-system-libxslt
--without-system-python --without-system-zlib --without-system-jars --without-system-stdlibs
--disable-crypt-link --disable-pam-link --disable-xrender-link --disable-randr-link
--without-openldap --without-system-xrender-headers --without-system-mesa-headers
--without-unix-wrapper --with-fonts --enable-minimizer --enable-presenter-console
--enable-pdfimport --without-system-poppler --enable-wiki-publisher --enable-report-builder
--with-extension-integration --with-linker-hash-style=both
--with-ant-home=/archive/cvs/libreoffice/build/build/apache-ant-1.8.1 --with-system-dicts
--with-external-dict-dir=/usr/share/hunspell --with-external-hyph-dir=/usr/share/hyphen
--with-external-thes-dir=/usr/share/mythes --with-dict=ALL --without-system-openssl
--with-distro=LibreOfficeLinux --with-git --with-max-jobs=16 --with-num-cpus=8
If you look closely, you see:
... --with-build-version=libreoffice-build 3.2.99.1 ...
instead of
... --with-build-version="libreoffice-build 3.2.99.1" ...
i.e. the quotes are missing, and I don't know why. Ideas?
Thanks,
Thomas
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.