On 10/9/12 10:03 PM, Ivan Cabrera wrote: (offlist) Generally we don't need to have logs for anything other than the specific package that fails to build. Logs of successful package builds in the chain are non-informative except on very rare occasions.
Your whole problem is here: > Scanning binaries for incorrect dyld linking... > ./test/.libs/a1-trap-test uses /usr/local/lib/libgomp.1.dylib > Please fix build process to get consistent use of fink's libraries. The message text isn't _quite_ right about the nature of the problem--it's not a problem with our build process as such in this case. It's essentially impossible to avoid having builds pick up stuff in /usr/local, and the build procedure is checking for that. In this case pixman links to libgomp from a third-party compiler that is installed there. Fortunately, the workaround is fairly simple. It's in the FAQ, but that site is down right now. 1) Rename /usr/local: sudo mv /usr/local /usr/local.moved 2) Do your "fink install gildas" 3) Put /usr/local back in place sudo mv /usr/local.moved /usr/local That will make sure that you get libgomp from your Xcode compiler instead. -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
