1106 2011-05-26 08:22:35 +0000 [x86-64] conflict getline declaration cause cvs compile failed 2011-05-31 02:01:20 +0000 1 1 6 Yocto Project Subprojects ADT adt 1.0 x86 x86_64 VERIFIED INVALID Medium normal 1.1 1 jiajun.xu liping.ke ke.yu lianhao.lu liping.ke poky.adt.watcher poky.watcher sgw --- --- --- oldest_to_newest 13996 0 jiajun.xu 2011-05-26 08:22:35 +0000 tree/branch: poky/1.1_M1 commit: fc55b224caa3eeac4abda099ec9ed505db59fb28 image location: all x86-64 images(sugarbay, jasperforest, qemux86-64) for 1.1_M1 RC1 http://autobuilder03.jf.intel.com/nightly/20110520-1/machines/qemu/qemux86_64/ With Yocto 1.1 M1 RC1 build, do make for cvs project in sdk image will meet conflict getline declaration and return fails. The error log is as below: ######### make: Warning: File `config.h' has modification time 31506048 s in the future make all-recursive make[1]: Entering directory `/home/root/cvs-1.11.23' Making all in lib make[2]: Entering directory `/home/root/cvs-1.11.23/lib' make[2]: Warning: File `.deps/yesno.Po' has modification time 31506048 s in the future gcc -DHAVE_CONFIG_H -I. -I.. -I../src -g -O2 -MT getline.o -MD -MP -MF .deps/getline.Tpo -c -o getline.o getline.c In file included from getline.c:25:0: getline.h:15:3: error: conflicting types for 'getline' /usr/include/stdio.h:671:20: note: previous declaration of 'getline' was here getline.c:158:1: error: conflicting types for 'getline' /usr/include/stdio.h:671:20: note: previous declaration of 'getline' was here make[2]: *** [getline.o] Error 1 make[2]: Leaving directory `/home/root/cvs-1.11.23/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/root/cvs-1.11.23' make: *** [all] Error 2 ######### To reproduce the bug, you should download cvs from http://ftp.gnu.org/non-gnu/cvs/source/stable/1.11.23/cvs-1.11.23.tar.bz2 and compile it in sdk image. The issue does not occur in x86 targets. 14062 1 liping.ke 2011-05-29 18:50:31 +0000 This is a known issue. And it should be the test project itself problem. We still leave this project in the previous testing because it's a typical project which could help us to find potential problems. If we find a better c project, big enough to find all potential problems, we can replace this project since it always has this error on x86-64 (In reply to comment #0) > tree/branch: poky/1.1_M1 > commit: fc55b224caa3eeac4abda099ec9ed505db59fb28 > image location: all x86-64 images(sugarbay, jasperforest, qemux86-64) for > 1.1_M1 RC1 > http://autobuilder03.jf.intel.com/nightly/20110520-1/machines/qemu/qemux86_64/ > > With Yocto 1.1 M1 RC1 build, do make for cvs project in sdk image will meet > conflict getline declaration and return fails. > > The error log is as below: > ######### > make: Warning: File `config.h' has modification time 31506048 s in the future > make all-recursive > make[1]: Entering directory `/home/root/cvs-1.11.23' > Making all in lib > make[2]: Entering directory `/home/root/cvs-1.11.23/lib' > make[2]: Warning: File `.deps/yesno.Po' has modification time 31506048 s in the > future > gcc -DHAVE_CONFIG_H -I. -I.. -I../src -g -O2 -MT getline.o -MD -MP -MF > .deps/getline.Tpo -c -o getline.o getline.c > In file included from getline.c:25:0: > getline.h:15:3: error: conflicting types for 'getline' > /usr/include/stdio.h:671:20: note: previous declaration of 'getline' was here > getline.c:158:1: error: conflicting types for 'getline' > /usr/include/stdio.h:671:20: note: previous declaration of 'getline' was here > make[2]: *** [getline.o] Error 1 > make[2]: Leaving directory `/home/root/cvs-1.11.23/lib' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/root/cvs-1.11.23' > make: *** [all] Error 2 > ######### > > To reproduce the bug, you should download cvs from > http://ftp.gnu.org/non-gnu/cvs/source/stable/1.11.23/cvs-1.11.23.tar.bz2 and > compile it in sdk image. > > The issue does not occur in x86 targets. 14071 2 jiajun.xu 2011-05-31 02:01:08 +0000 (In reply to comment #1) > This is a known issue. And it should be the test project itself problem. We > still leave this project in the previous testing because it's a typical project > which could help us to find potential problems. > > If we find a better c project, big enough to find all potential problems, we > can replace this project since it always has this error on x86-64 Thanks, Liping. Since it's an known issue, I think we could mark the bug as INVALID. We will use another version of cvs, which could pass compile on x86-64. 14072 3 jiajun.xu 2011-05-31 02:01:20 +0000 Verify the bug