On 13/12/10 16:39, Daniel Macks wrote: > > I've sen a few places where 10.4's linker is a bit more anal about > having dependent libs available at link-time. But it's always been > because a lib "somewhere in the dyld runtime loading tree" was missing a > direct link against a lib it used directly. On later 10.x, the default > is to look it up at runtime, on 10.4, the result is to crash at > build-time. Solution might be to specify for Assistant (the thing being > built here) to link directly against libQtCLucene.4.dylib.
You are so right, and when I build qt4-mac, it knows this, too, so it puts the right flags on the linker line (as I showed). The question is only: Under what circumstances can the -lQtCLucene disappear from the linker line, as it did for the poor newbie? If there were anything like a config.log or even some of the myriad files that cmake leaves behind when it makes Makefiles, I could look there and try to guess how that -lQtCLucene ends up in a Makefile in my case and not in the newbie's case. But I haven't yet found any trace of a check or directive or whatever that tells the underworld creature that produces Qt's Makefiles to put -lQtCLucene on a linker line. -- Martin ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
