
5 Oct
2010
5 Oct
'10
2:34 p.m.
On Mon, 04 Oct 2010 08:40:36 +0200, Rogan Dawes rogan@dawes.za.net wrote:
For what it is worth, would it be possible to have a more verbose error message that actually provides a reference to what needs to be done, rather than simply failing with an obscure message about DRAM configuration?
Maybe something like a file called e.g. CommonErrors containing common build and runtime errors and an explanation what might be the problem. A simple grep in this file for a few keywords shown in the build or run failure might provide helpful info then.
Regards,
--
Bas