On Sun, Jun 19, 2011 at 3:04 PM, Ibrahim Beicker <ibrabeicker@gmail.com> wrote:
This is a very noobish ask for help but when I tried to build
LibreOffice, the script autogen fails to detect 'fontconfig'
here's the output
checking for FONTCONFIG... no
configure: error: Package requirements (fontconfig >= 2.2.0) were not met:
No package 'fontconfig' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables FONTCONFIG_CFLAGS
and FONTCONFIG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I have the fontconfig 2.8.0, on Ubuntu 11.04 32 bits, I've followed
the steps on http://www.documentfoundation.org/develop/ and I searched
google but all I could find was bug reports having the same problem
but with other builds.
Is there any workaround for this?
See http://lists.freedesktop.org/archives/libreoffice/2011-April/010054.html
Since you use a recent mainstream distribution, you can take advantage
of the packaging
facilities to select and install all necessary development dependencies.
This single command,
sudo apt-get build-dep libreoffice
will install the necessary dependencies (including the fontconfig
development package) in one go.
Indeed, the wiki page at
http://wiki.documentfoundation.org/Development/Native_Build
should get a reference to the additional information that can be found at
http://www.libreoffice.org/get-involved/developers/
Simos
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.