Daniel Macks <dmacks <at> netspace.org> writes: > > On Mon, Feb 06, 2006 at 11:06:14PM -0800, Nathaniel Gray wrote: > > > > I don't know why the linker is so hell-bent on linking to /sw/lib/ > > libwmflite since the > > -L/Volumes/untitled/.../libwmf-0.2.8.2/src/.libs/ > > flag is present and that's where the library lives. > > > > Any ideas what I should do? > > There's a -L/sw/lib flag before that. Do you have any libwmf* there?
Nope. That's why the linker complains. > Maybe you have a previous version of the fink libwmf package > installed? Nope. This is the first time I've installed Fink on this system. > This is a fairly common bug, both by upstream authors and > by fink packagers trying to fix other upstream bugs. We don't yet have > a reasonably safe and clean way to test for it automatically:( I just > patched the libwmf package to be better at ignoring whatever libwmf > you may have installed. Once it propagates to your selfupdate server > and you selfupdate, you should be able to build libwmf (assuming the > original diagnosis was correct:) If you just can't wait, try > uninstalling libwmf (okay to leave its -shlibs and -bin component > packages). I worked around it by symlinking the library in .libs to /sw/lib. Then I hit a fun error where the version of gimp-print installed is too *new* for the version of gimp2. <sigh> Thanks for the help, -n8 PS: Please CC n8gray at caltech . edu with any replies. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
