libgee-0.6.2.1: error in pkg-plist
Koop Mast
kwm at rainbow-runner.nl
Sun Nov 13 16:37:36 UTC 2011
On 13-11-2011 15:49, Matthias Apitz wrote:
> El día Saturday, November 12, 2011 a las 03:35:25PM +0000, Chris Rees escribió:
>
>> This isn't a plist problem; it's an
>> autotools-doesn't-understand-FreeBSD-10 problem.
>>
>> On previous versions it works fine;
>>
>> [crees at pegasus]~/libgee% grep '^pkgconfigdir' work/libgee-0.6.2.1/Makefile
>> pkgconfigdir = $(prefix)/libdata/pkgconfig
>> [crees at pegasus]~/libgee%
> Seems so. If you do it step-by-step and check the Makefile for it it
> looks like this:
>
> caracas# make clean
> ===> Cleaning for libgee-0.6.2.1
>
> caracas# make extract
> ===> Vulnerability check disabled, database not found
> ===> License check disabled, port has not defined LICENSE
> ===> Extracting for libgee-0.6.2.1
> => SHA256 Checksum OK for libgee-0.6.2.1.tar.xz.
> caracas# grep '^pkgconfigdir' work/libgee-0.6.2.1/Makefile*
> work/libgee-0.6.2.1/Makefile.am:pkgconfigdir = $(libdir)/pkgconfig
> work/libgee-0.6.2.1/Makefile.in:pkgconfigdir = $(libdir)/pkgconfig
>
> caracas# make configure
> ...
> caracas# grep '^pkgconfigdir' work/libgee-0.6.2.1/Makefile*
> work/libgee-0.6.2.1/Makefile:pkgconfigdir = $(prefix)/libdata/pkgconfig
> work/libgee-0.6.2.1/Makefile.am:pkgconfigdir = $(libdir)/pkgconfig
> work/libgee-0.6.2.1/Makefile.in:pkgconfigdir =
> $(prefix)/libdata/pkgconfig
> work/libgee-0.6.2.1/Makefile.in.bak:pkgconfigdir = $(libdir)/pkgconfig
>
> caracas# make
> ...
> caracas# grep '^pkgconfigdir' work/libgee-0.6.2.1/Makefile*
> work/libgee-0.6.2.1/Makefile:pkgconfigdir = $(libdir)/pkgconfig
> work/libgee-0.6.2.1/Makefile.am:pkgconfigdir = $(libdir)/pkgconfig
> work/libgee-0.6.2.1/Makefile.in:pkgconfigdir = $(libdir)/pkgconfig
> work/libgee-0.6.2.1/Makefile.in.bak:pkgconfigdir = $(libdir)/pkgconfig
>
> as you see the 'make' changes the Makefile again produced by 'make
> configure', why? All the above is with UNAME_r set to 9.0-CURRENT;
>
> if you set in addition OSVERSION to 9.0, all is fine;
>
> matthias
This should be fixed by a commit done on wednesday. Can you update your
ports tree and try again?
-Koop
More information about the freebsd-ports
mailing list