You need to do a number of things anyway to prepare a machine for building openembedded. I have a git repository containing a script which will install all the packages I want to have on my machine. It will also build new versions of some applications.
When I install a new Ubuntu machine, i manually add synaptic, then add gnome + git + ssh keys. Then I download the script and let it run. Suggest you adopt a similar approach. Best Regards Ulf Samuelsson [email protected] +46 (722) 427 437 10 dec 2013 kl. 17:36 skrev Mats Kärrman <[email protected]>: > Hi, > > I have run into problems with make. > > Most things works fine with make v3.81 but when building a kernel recipe > (meta-fsl-arm linux-imx-3.10.9) > I consistently get: > > make: INTERNAL: Exiting with 5 jobserver tokens available; should be 4! > > To solve this I "manually" upgraded make on my machine to v3.82 which soon > brought new problems. > I then realized that OE-core got a recipe for make v3.82 with a number of > patches. After rebuilding > make using those patches, everything now seems to work fine :-D. > > It would be nice, however, if I didn't have to write detailed instructions > for everyone on how to patch > their machines in order to get their builds to work. Is it possible that OE > could build it's own make > to use the same way it compiles a new compiler using the existing one? > (building make v3.82 using > make v3.81 works fine;) > > BR // Mats > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-core _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
