Bug 32195

Summary: use absolute path for gperf
Product: LibreOffice Reporter: bapt <bapt>
Component: LibreofficeAssignee: Not Assigned <libreoffice-bugs>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: medium CC: gautier.sophie, thb
Version: 3.3.0 RC1   
Hardware: Other   
OS: FreeBSD   
Whiteboard:
i915 platform: i915 features:
Attachments: patch (as pushed to master)

Description bapt 2010-12-07 12:50:08 UTC
On FreeBSD we have an old (to old for libreoffice) version of gperf in base (/usr/bin/gperf) and we can install a newer version from ports (/usr/local/bin/gperf)

by default the configure script fails finding the old version of gperf.
if I set GPERF=/usr/local/bin/gperf before the configure script it finds the newer one and is happy.

but building libreoffice fails. because the following files :

filter/source/svg/makefile.mk
oox/source/token/makefile.mk
writerfilter/source/ooxml/makefile.mk

uses gperf from path.

Two work around are possible : declare /usr/local/bin first in path or replace gperf by /usr/local/bin/gperf in those files.

The best thing would be to use the absolute path of the detected gperf (sorry I don't have a patch for that)
Comment 1 Rene Engelhard 2010-12-08 05:01:52 UTC
sounds we should AC_SUBST([GPERF]) in configure.in after the check and then just
use $(GPERF) in the makefile
Comment 2 Robert Nagy 2010-12-10 13:51:50 UTC
I agree with Rene, that's the correct way.
Comment 3 Thorsten Behrens 2010-12-10 14:07:14 UTC
Any takers for cooking up a patch?
Comment 4 Rene Engelhard 2010-12-13 11:26:11 UTC
thorsten: yes, me :)
Comment 5 Rene Engelhard 2010-12-13 13:20:56 UTC
Created attachment 41086 [details] [review]
patch (as pushed to master)

this patch should do it (also committed and pushed to master)
Comment 6 Rene Engelhard 2010-12-13 13:21:44 UTC
-> RESOLVED
Comment 7 Rene Engelhard 2010-12-14 06:28:06 UTC
now also in libreoffice-3-3 (-> will be fixed in rc2)
Comment 8 sophie 2011-01-13 08:47:25 UTC
Closing - Sophie

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.