Date: Tue, 14 Feb 2017 12:37:06 +0100 From: Tijl Coosemans <tijl@coosemans.org> To: Dave Horsfall <dave@horsfall.org> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Problem with building libgcrypt Message-ID: <20170214123706.78d66c28@kalimero.tijl.coosemans.org> In-Reply-To: <alpine.BSF.2.20.1702141503220.46495@aneurin.horsfall.org> References: <alpine.BSF.2.20.1702122055080.46495@aneurin.horsfall.org> <20170212121812.49432548@kalimero.tijl.coosemans.org> <alpine.BSF.2.20.1702131855170.46495@aneurin.horsfall.org> <20170213113556.1913eea4@kalimero.tijl.coosemans.org> <alpine.BSF.2.20.1702141151410.46495@aneurin.horsfall.org> <alpine.BSF.2.20.1702141503220.46495@aneurin.horsfall.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 14 Feb 2017 15:11:30 +1100 (EST) Dave Horsfall <dave@horsfall.org> wrote: >>> What is the output of "pkg which /usr/local/lib/libiconv.la"? >> >> Not found; I sense a generic approach to any more errors of this type :-) > > Removed as suggested (along with libxslt) as nothing claimed to be using > it, now it's complaining that they're missing when building graphics/peps > (I gave docbook a miss): > > libtool: error: cannot find the library '/usr/local/lib/libiconv.la' or > unhandled argument '/usr/local/lib/libiconv.la' > > Why is libiconv.la now suddenly required? > > At this rate it'll be a full install, but that is definitely a last > resort (and the 10.3 CD I burned had better be readable). Keep following the 20140909 entry in UPDATING. You should run this command now: find /usr/local/lib -name '*.la' | xargs grep -l 'libiconv\.la' | xargs pkg which
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170214123706.78d66c28>