I decided to built the SDK to play around with the output so I can understand how it all goes together. According to the documentation, I simply do:
bitbake <image> -c populate_sdk It's worth noting I am running a custom image and distro and not a poky/yocto image (I do inherit core-image, however). I don't spot any critical differences between core-image-minimal and my custom image. My distro conf includes poky.conf to pull in most of the configuration. However, the first thing I get is this: DEBUG: Executing python function sysroot_cleansstate DEBUG: Python function sysroot_cleansstate finished DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common'] DEBUG: Executing shell function autotools_preconfigure DEBUG: Shell function autotools_preconfigure finished DEBUG: Executing python function autotools_copy_aclocals DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common'] DEBUG: Python function autotools_copy_aclocals finished DEBUG: Executing shell function do_configure configure.ac:34: error: Please use exactly Autoconf 2.64 instead of 2.69. config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from... configure.ac:34: the top level for the binutils-crosssdk do_configure task. Am I doing something insane? I figure since my image build is working correctly, it should be using the right versions of autoconf, etc.
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
