On 23 January 2012 17:42, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
On 23 January 2012 17:07, Darrell Anderson humanreadable@yahoo.com wrote:
OK, post the full build log
somewhere. I suspect an
#included file is not being found.
tdelibs build log:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13....
A little strange. That first log was run with NUMJOBS=-j1.
I ran a second time with NUMJOBS=-j3 and the errors were different:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13....
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
tdelibs cannot be run with multiple jobs.
Umm...yes it can. I run it that way all the time on an 8 core build machine.
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
wow really? I was almost sure. bad memory maybe
Autotools was restricted to -j1, but CMake can work with as many cores as you can give it.
Tim