Robert Cruikshank wrote: [] >>> i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libpng12.0.26.0.dylib: No >>> such file or directory
This is not the same problem as before (that was with libXrandr). When I wrote that the libXrandr problem was solved by installing xcode-3.1, I did not yet know that a whole lot of new problems were introduced, among them with libpng12, with libXdamage, with freetype... [] > It's a brand new Mac Pro and all I've installed tool wise is xcode 3.0 > then xcode 3.1? Yes, Apple screwed this up in a big way: If you do what you did, simply install xcode-3.1 on an otherwise standard Leopard system, you cannot compile most software that links to X11. They are aware of this, but don't expect them to move very quickly. OTOH, if you install the xquartz X11 update (now at version 2.3.0), you cannot compile most software that uses X11, either, but that's a different story, and Fink has already fixed many (most?) of its packages that suffer from this. And if you install the xquartz update *without* removing /usr/X11 first, then you don't even notice the new problem. That's what I would currently recommend (until other bugs raise their heads): Install (or leave installed) the standard X11 from the system DVD, plus any Apple updates, including xcode-3.1 or not, and then install the xquartz-2.3.0 update on top of it. -- Martin ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
