Re: USES=pathfix broken?
On Sun, Jan 22, 2017 at 08:46:49AM +0100, Antoine Brodin wrote: > On Sun, Jan 22, 2017 at 8:40 AM, Don Lewiswrote: > > I've started getting a bunch of pkg-fallout@ email reporting missing > > libdata/pkgconfig/*.pc files. It looks like the *.pc files are getting > > installed under lib/pkgconfig. > > > > [snip] > > /bin/mkdir -p > > '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' > > install -m 0644 mtbl/libmtbl.pc > > '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' > > [snip] > > ===> Building package for mtbl-0.8.0 > > pkg-static: Unable to access file > > /wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/libdata/pkgconfig/libmtbl.pc: > > No such file or directory > > [snip] > > > > So far the problems have been with limited to > > [package - head-amd64-default] and > > [exp - 103i386-default-build-as-user]. The latter would seem to > > eliminate the recent sed changes in -CURRENT as a cause. I'm not seeing > > any problems with the r432015 revision of the ports tree, and I don't > > see any suspicious commits to ports/Mk after that point. > > > Hi, > > There seems to be a regression in pkgconf 1.2.0, see > https://github.com/pkgconf/pkgconf/issues/108 > Fixed thanks for reporting! (both upstream and in ports) Best regards, Bapt signature.asc Description: PGP signature
Re: USES=pathfix broken?
On Sun, Jan 22, 2017 at 8:40 AM, Don Lewiswrote: > I've started getting a bunch of pkg-fallout@ email reporting missing > libdata/pkgconfig/*.pc files. It looks like the *.pc files are getting > installed under lib/pkgconfig. > > [snip] > /bin/mkdir -p > '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' > install -m 0644 mtbl/libmtbl.pc > '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' > [snip] > ===> Building package for mtbl-0.8.0 > pkg-static: Unable to access file > /wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/libdata/pkgconfig/libmtbl.pc: > No such file or directory > [snip] > > So far the problems have been with limited to > [package - head-amd64-default] and > [exp - 103i386-default-build-as-user]. The latter would seem to > eliminate the recent sed changes in -CURRENT as a cause. I'm not seeing > any problems with the r432015 revision of the ports tree, and I don't > see any suspicious commits to ports/Mk after that point. Hi, There seems to be a regression in pkgconf 1.2.0, see https://github.com/pkgconf/pkgconf/issues/108 Antoine ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
USES=pathfix broken?
I've started getting a bunch of pkg-fallout@ email reporting missing libdata/pkgconfig/*.pc files. It looks like the *.pc files are getting installed under lib/pkgconfig. [snip] /bin/mkdir -p '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' install -m 0644 mtbl/libmtbl.pc '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' [snip] ===> Building package for mtbl-0.8.0 pkg-static: Unable to access file /wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/libdata/pkgconfig/libmtbl.pc: No such file or directory [snip] So far the problems have been with limited to [package - head-amd64-default] and [exp - 103i386-default-build-as-user]. The latter would seem to eliminate the recent sed changes in -CURRENT as a cause. I'm not seeing any problems with the r432015 revision of the ports tree, and I don't see any suspicious commits to ports/Mk after that point. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"