Date: Tue, 17 Sep 2013 07:36:37 +0000 From: "C. L. Martinez" <carlopmart@gmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: syslog-ng33 fails to build Message-ID: <CAEjQA5KC2=JOLgcfw5zO4iZzTueKxPHQcoYZ3PHug=wpvWORrg@mail.gmail.com> In-Reply-To: <52364575.3030500@cyberleo.net> References: <CAEjQA5%2B6ae1_z5L6d2g3NY6ggq8vEVf-cm5690hGFY6TEAEbTw@mail.gmail.com> <52364575.3030500@cyberleo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 15, 2013 at 11:40 PM, CyberLeo Kitsana <cyberleo@cyberleo.net> wrote: > On 09/13/2013 01:53 AM, C. L. Martinez wrote: >> Hi all, >> >> I am trying to build syslog-ng33 (release 3.3.9) using a poudriere >> server, but build process fails: >> > <snip> >> configure: error: in >> `/wrkdirs/usr/ports/sysutils/syslog-ng33/work/syslog-ng-3.3.9': >> configure: error: The pkg-config script could not be found or is too >> old. Make sure it >> is in your PATH or set the PKG_CONFIG environment variable to the full >> path to pkg-config. >> >> Alternatively, you may set the environment variables EVTLOG_CFLAGS >> and EVTLOG_LIBS to avoid the need to call pkg-config. >> See the pkg-config man page for more details. >> >> It is strange, because previous build (on August 27) works without problems ... >> >> Any idea?? > > Probably because syslog-ng relies upon pkgconfig, but assumes it will be > installed by one of the dependent ports so doesn't explicitly declare > the dependency. Poudriere has a habit of only installing the immediate > dependencies of the package it is currently compiling, so exposes such > issues when a port is updated, but none of its dependencies are. Bug > ports/181098 is another I found like this. > > Add this to the port's Makefile after the include of bsd.port.options.mk: > > USES+= pkgconfig > > If that corrects the issue you're seeing, submit a pr. > > -- > Fuzzy love, > -CyberLeo > Technical Administrator > CyberLeo.Net Webhosting > http://www.CyberLeo.Net > <CyberLeo@CyberLeo.Net> > Many thanks CyberLeo ... It works. I have opened pr last week about this (but instead against syslog-ng33, it is about syslog-ng 3.4.3, but the problem is the same) http://www.freebsd.org/cgi/query-pr.cgi?pr=182061
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEjQA5KC2=JOLgcfw5zO4iZzTueKxPHQcoYZ3PHug=wpvWORrg>