Tree/Branch: Poky/Master Poky Commit: 7cd2ac0e40d854bab9a32512018aff6172500c0e With latest yocto tree, cvs configure fail with i686-mips or x86_64-mips toolchain. The error message is as below. The culprit is that cvs_cv_func_printf_ptr is not set in site/mips-commmon. For other targets, like arm and ppc, it is set for them. #### checking for working fork... cross configure: WARNING: result yes guessed because of cross compilation checking for working vfork... (cached) yes checking whether closedir returns void... yes checking for library containing getspnam... none required checking whether utime accepts a null argument... no checking for long file names... yes checking whether printf supports %p... configure: error: cannot run test program while cross compiling See `config.log' for more details. ####
Seems the following patch from Khem failed to be merged Module: openembedded.git Branch: org.openembedded.dev Commit: df9cb262d95bacb06192dcf69b303e4088557832 URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=df9cb262d95bacb06192dcf69b303e4088557832 Author: Khem Raj <raj.khem at gmail.com> Date: Fri Jun 4 18:00:56 2010 -0700 site/mips-common: Cache cvs_cv_func_printf_ptr Signed-off-by: Khem Raj <raj.khem at gmail.com> --- site/mips-common | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/site/mips-common b/site/mips-common index 47a34e2..4b18c84 100644 --- a/site/mips-common +++ b/site/mips-common @@ -1,6 +1,9 @@ ac_cv_func_realloc_0_nonnull=${ac_cv_func_realloc_0_nonnull=yes} ac_cv_func_malloc_0_nonnull=${ac_cv_func_malloc_0_nonnull=yes} +# cvs +cvs_cv_func_printf_ptr=${cvs_cv_func_printf_ptr=yes} + # screen screen_cv_sys_bcopy_overlap=${screen_cv_sys_bcopy_overlap=no} screen_cv_sys_memcpy_overlap=${screen_cv_sys_memcpy_overlap=no}
Working with Khem to port his patch from openembedded to oe-core
Verified with mips toolchain on nightly build 20110709-1, and this bug does NOT occur. Build location: http://autobuilder02.yoctoproject.org/nightly/20110709-1/toolchain Gitinfo: commit 8df2a558b4d61778a669705b867969abe3514846
mark the bug as verified according to the last comments