Am Saturday, 20. August 2011 schrieben Sie: Hi Martin,
> If your SHR makefile allowed to call setup-shr-stable, then it was very > old and maybe broken, see: > http://git.shr-project.org/git/?p=shr-makefile.git;a=commit;h=7fc9adc59b77b > c64f81f1a5f70a7982aebcd42e9 Then maybe that's part of the problem. Just wget http://build.shr-project.org/Makefile and see for yourself. setup- shr-stable is still there. > Have you tried shr-chroot as described in that wiki page? Yes, that's what I did (I followed all its instructions). > I'm not building shr-unstable or shr-testing anymore (only shr-core > where you won't find jamvm yet), but lately there were reports about > bitbake master (1.13.3) handling depends with old OE (shr-u, shr-t) > badly. Please try to downgrade bitbake by switching bitbake branch from > master to 1.12 or 1.10. Thanks, I will try that. > This should be fixed yesterday by: > http://git.shr-project.org/git/?p=shr-makefile.git;a=commit;h=e1e95b0f611fb > cf513437b2726bbdb3999908546 but that will fix only new checkouts, you can > fix yours by > echo "../../../../openembedded/.git/objects/" > > .git/objects/info/alternates in ie shr-unstable/openembedded directory Thanks :-) > many packages needs their -native version to cross compile (ie when they > build some tool used later in tests or for build itself) to see what > exactly pulls native X11 for jamvm use "bitbake -g jamvm" Done, I'll install graphviz next... > "C compiler cannot create executables" is usually sign of something > wrong with cross toolchain, > see clean_toolchain alias in > http://git.shr-project.org/git/?p=shr-chroot.git;a=blob;f=OE/.bashrc;h=4ec0 > 7433895502545399b6275639db84675fa5a0;hb=HEAD to rebuild toolchain Yes, the strange thing is, that I get this error, *after* successfully building lots of other packages. Best wishes, Christine _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
