Date: Fri, 5 Aug 2011 10:41:54 +0200 From: Ewald Jenisch <a@jenisch.at> To: <bf1783@gmail.com> Cc: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: portupgrades fail because of missing /usr/local/lib/liblzma.la Message-ID: <20110805084154.GA46719@aurora.oekb.co.at> In-Reply-To: <CAGFTUwOhdUXwoiB86KeYSj3Ycj6hu-L1VuQAqbkRcyh_LDPGzQ@mail.gmail.com> References: <CAGFTUwOhdUXwoiB86KeYSj3Ycj6hu-L1VuQAqbkRcyh_LDPGzQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 04, 2011 at 01:45:02PM -0400, b. f. wrote: > > o) What can I do to get ports recognize the correct location of the > > xz-libraries? > > As I wrote above, some more information would help. I'm guessing that > you have a port that (unfortunately) uses libtool to perform linking, > and has an erroneous /usr/local/lib/lzma.la entry in a libtool archive > file (*.la), or is using some combination of uncommon linker flags > and sloppy use of -L/usr/local/lib. Does a search like: > > fgrep -e lzma -nHr /usr/local/lib --include='*.la' > > yield any results? If you see any references in a libtool archive to > the nonexistent "/usr/local/lib/liblzma.la", try removing and then > rebuilding the port that owns that libtool archive -- you should be > able to determine the port by running "pkg_info -W" with the full path > of the libtool archive as an argument. > Hi, First of all I'm posting my reply to both -questions where I sent my original question to as well as -ports where you sent your reply so others are seeing this too. In short - thanks to your hints everything's healthy again :-)) Here's what I did (in case others are suffering from this problem too): fgrep -e lzma -nHr /usr/local/lib --include='*.la' yielded a bunch of results - grep-ed for "/usr/local/lib/liblzma.la". Then feeded these into pkg_info -W which nicely pointed me to the corresponding port where this library comes from. The only thing I had to do then was to make deinstall;make clean; make install this port. In my case it was e.g. the "ImageMagick-6.7.0.10_1" port causing all the mess. So thanks to you all who responded. It's great to have such a knowledgeable and helpful community out there - you indeed learn something new every day. -ewald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110805084154.GA46719>