On 02/19/2013 03:33 PM, Takeshi Hamasaki wrote:
Then I recommend to look into log files. For my case, after executing commands:

$ bitbake package-index -c cleansstate
$ bitbake -D -D package-index > bitbake-d-d.package-index 2> errlog

I have at least four log files.
1. bitbake-d-d.package-index in current dir
2. errlog   in current dir
3. run.do_package_index.* in
build/tmp-angstrom_v2012_05-eglibc/work/armv5te-angstrom-linux-gnueabi/package-index-1.0-r0
4. log.do_package_index.* in
build/tmp-angstrom_v2012_05-eglibc/work/armv5te-angstrom-linux-gnueabi/package-index-1.0-r0

(Actually, I skipped to generate 2., my build succeed.)
I guess you can find some clue looking into 4., 3., and maybe 1.

I attach mine to this mail, and hope they might be some help for you.
Thanks for all your help!
I've been comparing the run.do_package_index file from myself and from the buildserver. If I look at it the only real difference (besides paths etc) are in the SHELL
> export SHELL="/usr/local/bin/bash-wrapper"
< export SHELL="/bin/bash"
I will ask my administrator to change it and will retry.



_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Reply via email to