219 2010-08-19 14:17:57 +0000 dpkg does not build properly 2010-12-21 06:09:41 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 0.9 x86 Multiple RESOLVED FIXED Low normal 0.9 M4 1 mark.hatle dongxiao.xu kevin.tian meta.mr.watcher meta.watcher richard.purdie sgw --- --- --- oldest_to_newest 9336 0 mark.hatle 2010-08-19 14:17:57 +0000 I experienced a build failure when attempting to set my default package type to package_deb. While building for a qemuppc machine type: | checking for unistd.h... (cached) yes | checking whether sys_siglist is declared... (cached) yes | checking whether compiler supports __attribute__... yes | checking for va_copy... configure: error: in `/.../git/poky/build/tmp/work/ppc603e-poky-linux/dpkg-1.14.19-r7/ dpkg-1.14.19': | configure: error: cannot run test program while cross compiling | See `config.log' for more details. | FATAL: oe_runconf failed NOTE: package dpkg-1.14.19-r7: task do_configure: Failed I assume this affects other architectures as well as PPC. 9339 1 kevin.tian 2010-08-19 23:20:18 +0000 Mark, you may try adding below lines to meta/site/powerpc-common: dpkg_cv_va_copy=${ac_cv_va_copy=yes} dpkg_cv___va_copy=${ac_cv___va_copy=yes} We can't run tests in cross-compile environment, and thus site files jump out to workaround them. Now va_copy is only set for x86 and arm, perhaps because they're only platform previously focused on Having said that, I don't have idea whether 'yes' or 'no' should be set for powerpc platform. :/ For example, x86 sets va_copy to 'no' while arm sets it to 'yes'. I'm not sure the efficient way to figure it out. You may need check ppc stdarg.h for decision Richard may comment more here. :-) 9471 2 dongxiao.xu 2010-08-30 22:28:15 +0000 Kevin's method could solve this configure error. I'm also interested in how to set the meta/site files for each platform. Bug 243 also have similar setting problems. Richard, could you give some comments on it? 9480 3 richard.purdie 2010-08-31 14:15:17 +0000 Adding entries to the site file is the correct answer. Sometimes you may know the answer and can add the entry. In other cases you can try building the application in a qemu sdk image and then take the correct result from there (or run a test on real hardware if you have it)