On 4/6/13 3:45 AM, Peter Dyballa wrote: > > Am 06.04.2013 um 10:47 schrieb Eduardo Pestana: > >>> make[1]: *** Waiting for unfinished jobs.... >> > > This can indicate that you should not use > >>> Max. Fink build jobs: 2 >> > > but reduce the number to one. At least you could give it a try and see > whether the build still fails. > > One big advantage of one compilation process is that a possible error is > exactly indicated and not mixed with other compiler or linker output. > > -- > Greetings > > Pete > > A census taker is a man who goes from house to house increasing the > population. > > > >
Right. It's pretty common for one thread of a build to fail but the rest to keep on going for a while. Your output looks to me like one of those cases. That's one reason the output text suggests trying again with one job. The other, which probably doesn't apply here, is that some builds don't really work with multiple threads, and we'd like to know that. It's not uncommon for a failure to show up which doesn't maintainer's machine. Anyway, definitely try the build again with a single build job, since at the very least the failure should be easier to diagnose. -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ 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
