On Wed, Dec 10, 2014 at 3:16 AM, Maarten Hoes <hoes.maarten@gmail.com> wrote:
Hrm.
It appears I get the openldap build error when I do the build like this
(like it happens with the tb script) :
$ LDFLAGS+='-fprofile-arcs'
$ CFLAGS+='-fprofile-arcs -ftest-coverage'
$ CXXFLAGS+='-fprofile-arcs -ftest-coverage'
$ CPPFLAGS+='-fprofile-arcs -ftest-coverage'
$ export LDFLAGS CFLAGS CXXFLAGS CPPFLAGS
$ ./autogen.sh --enable-python=internal --disable-online-update
--without-system-libs --without-system-headers
$ make build-nocheck
But not when I do the build like this (like I do on the cmdline, or is done
in the lcov-report.sh script) :
$ LDFLAGS+='-fprofile-arcs' CFLAGS+='-fprofile-arcs -ftest-coverage'
CXXFLAGS+='-fprofile-arcs -ftest-coverage' \
CPPFLAGS+='-fprofile-arcs -ftest-coverage' ./autogen.sh
--enable-python=internal --disable-online-update \
--without-system-libs --without-system-headers
$ make build-nocheck
then the easiest work around is to define a custom phase for that
profile that overide the configure (aka autogen) step
so that it does it the second way (and remove the *FLAGS from the
profile's config
Norbert
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.