Compilation error when building PPC64-LE CirrOS image

Bug #1662949 reported by Tiago Mello
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CirrOS
New
Undecided
Unassigned

Bug Description

I followed the instruction in the doc/README-powerpc.txt.
Command used: export ARCHES="ppc64le powerpc ppc64"; ./bin/build-release daily

Got the follow error:

make[2]: Entering directory '/tmp/build-d170207/build/ppc64le/buildroot/build/host-ncurses-5.9/progs'
cd ../ncurses; /usr/bin/make
make[3]: Entering directory '/tmp/build-d170207/build/ppc64le/buildroot/build/host-ncurses-5.9/ncurses'
/tmp/build-d170207/build/ppc64le/buildroot/host/usr/bin/ccache /usr/local/bin/gcc -DHAVE_CONFIG_H -I../ncurses -I. -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include -D_GNU_SOURCE -DNDEBUG -I. -I../include -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include/ncurses -O2 -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include --param max-inline-insns-single=1200 -fPIC -c ../ncurses/lib_gen.c -o ../obj_s/lib_gen.o
/tmp/build-d170207/build/ppc64le/buildroot/host/usr/bin/ccache /usr/local/bin/gcc -DHAVE_CONFIG_H -I../ncurses -I. -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include -D_GNU_SOURCE -DNDEBUG -I. -I../include -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include/ncurses -O2 -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include --param max-inline-insns-single=1200 -fPIC -c ../ncurses/./base/lib_getstr.c -o ../obj_s/lib_getstr.o
/tmp/build-d170207/build/ppc64le/buildroot/host/usr/bin/ccache /usr/local/bin/gcc -DHAVE_CONFIG_H -I../ncurses -I. -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include -D_GNU_SOURCE -DNDEBUG -I. -I../include -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include/ncurses -O2 -I/tmp/build-d170207/build/ppc64le/buildroot/host/usr/include --param max-inline-insns-single=1200 -fPIC -c ../ncurses/./base/lib_hline.c -o ../obj_s/lib_hline.o
_9154.c:758:3: error: "_Bool" after # is not a positive integer
_9154.c:764:3: error: "_Bool" after # is not a positive integer
_9154.c:770:3: error: "_Bool" after # is not a positive integer
_9154.c:776:3: error: "_Bool" after # is not a positive integer
_9154.c:782:3: error: "_Bool" after # is not a positive integer
_9154.c:788:3: error: "_Bool" after # is not a positive integer
_9154.c:794:3: error: "_Bool" after # is not a positive integer
_9154.c:800:3: error: "_Bool" after # is not a positive integer
_9154.c:806:3: error: "_Bool" after # is not a positive integer
_9154.c:812:3: error: "_Bool" after # is not a positive integer
_9154.c:818:3: error: "_Bool" after # is not a positive integer
_9154.c:824:3: error: "_Bool" after # is not a positive integer
_9154.c:836:3: error: "_Bool" after # is not a positive integer
In file included from ../ncurses/curses.priv.h:283:0,
                 from ../ncurses/lib_gen.c:19:
_9154.c:837:2: error: expected ‘)’ before ‘int’
Makefile:795: recipe for target '../obj_s/lib_gen.o' failed
make[3]: *** [../obj_s/lib_gen.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/tmp/build-d170207/build/ppc64le/buildroot/build/host-ncurses-5.9/ncurses'
Makefile:307: recipe for target '../lib/libncurses.so' failed
make[2]: *** [../lib/libncurses.so] Error 2
make[2]: Leaving directory '/tmp/build-d170207/build/ppc64le/buildroot/build/host-ncurses-5.9/progs'
package/pkg-generic.mk:156: recipe for target '/tmp/build-d170207/build/ppc64le/buildroot/build/host-ncurses-5.9/.stamp_built' failed
make[1]: *** [/tmp/build-d170207/build/ppc64le/buildroot/build/host-ncurses-5.9/.stamp_built] Error 2
make[1]: Leaving directory '/tmp/cirros/buildroot-2015.05'
Makefile:70: recipe for target '/tmp/cirros/../build-d170207/build/ppc64le/buildroot/images/rootfs.tar' failed
make: *** [/tmp/cirros/../build-d170207/build/ppc64le/buildroot/images/rootfs.tar] Error 2

Revision history for this message
Tiago Mello (timello) wrote :

Scott,

I would appreciate any advise.

Thank you,

Tiago

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.