On Wed, 2011-06-01 at 16:06 +0100, Phil Blundell wrote: > On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote: > > I'd like to collect some feedback on error messages while building that > > you find confusing/annoying/unhelpful. I'm going to be working on trying > > to improve the situation and would like to hear from you about what > > could be more helpful. > > Funnily enough we were just having a discussion about this on irc. My > personal top two least favourite diagnostics are:
Another non-favourite: if you fail to specify the right protocol for the git fetcher then you end up with something like: ERROR: Function 'Fetcher failure for URL: 'None'. Fetch command export HOME="/home/pb"; export GIT_CONFIG="/home/pb/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/etc/gitconfig"; export PATH="..."; git ls-remote rsync://gitolite@cam-git/pb/linux-2.6.35 master failed with signal 128, output: fatal: Could not make temporary directory: No such file or directory ' failed Usually the value of $PATH is about half a screenful so this error looks more monstrous in real life than it probably does above, and it isn't immediately apparent that the "no such file or directory" thing is a result of having tried to fetch with the wrong URI scheme. This is made slightly more irritating by the fact that there isn't much consistency between the different fetchers about the URI structure; some of them want a "proto" attribute whereas others (including git) want "protocol", so it's harder than perhaps it ought to be to remember what the correct naming is. p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
