Date: Mon, 31 Dec 2012 17:14:25 -0800 (PST) From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: freebsd-ports@freebsd.org Subject: Re: Two errors each affecting several ports Message-ID: <1357002865.4322.YahooMailClassic@web164004.mail.gq1.yahoo.com> In-Reply-To: <CAN6yY1vEiLx_3zLx88-6FS3qZns22R0fk0Nd7S8dbaB%2B8%2BnbXQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Reply below. --- On Mon, 12/31/12, Kevin Oberman <kob6558@gmail.com> wrote: From: Kevin Oberman <kob6558@gmail.com> Subject: Re: Two errors each affecting several ports To: "Jeffrey Bouquet" <jeffreybouquet@yahoo.com> Cc: freebsd-ports@freebsd.org Date: Monday, December 31, 2012, 3:37 PM On Mon, Dec 31, 2012 at 3:13 PM, Jeffrey Bouquet <jeffreybouquet@yahoo.com> wrote: > First error: > 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 > (affects ports such as shared-mime-info, esound...) pkg-config was replaced by pkgconf back in July. Check /usr/ports/UPDATING for the 20120726:entry. Either you didn't relace it or, more likely, you did not follow the instructions in UPDATING. > Second error: > /usr/local/bin/ld: main.o: undefined reference to symbol 'curses version' > /usr/local/lib/libtinfow.so.6.0: could not read symbols: Invalid operatio= n > collect2: ld returned 1 exit status > *** [mutt] Error code 1 > ... > Which affects several other ports (... mc, vitunes...) > ... > I tried rebuilding binutils to fix it/them, no difference.=A0 (BTW binuti= ls needs several > of its binaries (/usr/local/bin/ to configure/build/install, I fixed that= temporarily by > copying some of them elsewhere and back as "extra binaries" until reinsta= lled and > overwritten...) > ... > Each of these three errors may be specific to some arcane setup here.=A0 = Posting in > the chance that others have fixed it/them and so it is more common proble= m(s). Yes, it appears that something specific to your environment is making ports unhappy, but I have no idea what. You don't say what version of FreeBSD or whether you have moved to pkgng or are still using the old pkg_* tools. Not that I am sure I would know what was going on with this information, but it would certainly help. The issue with binutils is especially odd. Could you state what "extra binaries" were a problem? It almost sounds like some sort of tool chain issue. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com 9-STABLE, (r243371); I am not yet pkgng; I've lots in /usr/local/lib/compat and some in /usr/local/lib/compat/pkg... the binaries binutils complains ab= out are as, ar, and ranlib.; standard $PATH;=A0 I replaced pkg-config with pkgc= onf ages ago.=A0 (Almost wishing for a "wrapper port" that one wraps around a port b= uild to point explicitly at which dependency causes an error, or if not, which para= meter to ./configure or which patch file in /files/ or which line in the Ma= kefile... almost like a dtrace/strace GUI-something... but specifically for= port building.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1357002865.4322.YahooMailClassic>