Hi, On Wed, 2014-09-10 at 15:46 -0400, Hans-Peter Nilsson wrote: > (Thanks to people CC'ed and others forgotten; I hope I > incorporated at least some of everyone's suggestions.) > > [...] > Also, the idea of using a *combined* tree here, has been challenged, > so I toned down the wording from the actual "require" to the > negation(!) and added an apologetic blurb.
It says: "Testing with a simulator makes use of a combined tree here; you can't easily build newlib, required for simulator testing,..." I don't understand why newlib can't be built for simulator testing easily outside of a combined tree. Are you referring to the separate make all-gcc - build newlib - continue with full gcc build? Or is it just a coincidence that it works rather easily on SH? " other alternatives exist. For example, binutils and simulators can be built for the target, and installed beforehand." I still think we should somehow document how to do that. The info is scattered out there on the net, but it'd be easier to have it on the official doc pages. Cheers, Oleg
