On 10/3/2013 12:59 PM, Richard Miles wrote: > collect2: ld returned 1 exit status > make[2]: *** [lib/libkdeui.5.4.0.dylib] Error 1 > make[2]: Leaving directory > `/sw/src/fink.build/kdelibs4-x11-4.4.1-4/kdelibs-4.4.1/build' > make[1]: *** [kdeui/CMakeFiles/kdeui.dir/all] Error 2 > make[1]: Leaving directory > `/sw/src/fink.build/kdelibs4-x11-4.4.1-4/kdelibs-4.4.1/build' > make: *** [all] Error 2 > ### execution of /tmp/fink.3Oxpj failed, exit code 2 > ### execution of /tmp/fink.ijuzT failed, exit code 2 > Thats all the ### I could see
Again, this is not useful because you're not including the compiler command that led to the failure, only a generic "something failed here" output. Alex's instructions (and the build failure output) were clear: include the compiler line "generally starting with g++". In this case, search the build output for "-o ../lib/libkdeui.5.4.0.dylib", then paste here that entire command line (it's pretty long). Hanspeter ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ 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
