Re: [Qemu-devel] [PATCH v2] libcacard: fix compile error on glib2-2.12.3-4.el5

[Paolo Bonzini]

Il 30/09/2014 15:57, Zhi Yong Wu ha scritto:
> libtool  --mode=link --tag=CC c++ -m64 -D_GNU_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes
> -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes
> -fno-strict-aliasing -fno-common  -Wendif-labels
> -Wmissing-include-dirs -Wnested-externs -Wformat-security -Wformat-y2k
> -Winit-self -Wold-style-definition -fstack-protector-all
> -I/usr/include/libpng12   -I/home/zhiyong.wzy/qemu/pixman/pixman
> -I/home/zhiyong.wzy/qemu/pixman/pixman  -I/home/zhiyong.wzy/qemu/tests
> -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include   -g
> -Wl,--warn-common -m64 -g  -o vscclient libcacard/vscclient.o
> libcacard.la    -Wc,-fstack-protector-all  -lm -pthread -L/lib64
> -lgthread-2.0 -lglib-2.0    -lz -lrt -lz -luuid  -lutil
> c++ -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings
> -Wmissing-prototypes -fno-strict-aliasing -fno-common -Wendif-labels
> -Wmissing-include-dirs -Wnested-externs -Wformat-security -Wformat-y2k
> -Winit-self -Wold-style-definition -fstack-protector-all
> -I/usr/include/libpng12 -I/home/zhiyong.wzy/qemu/pixman/pixman
> -I/home/zhiyong.wzy/qemu/pixman/pixman -I/home/zhiyong.wzy/qemu/tests
> -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g
> -Wl,--warn-common -m64 -g -o .libs/vscclient libcacard/vscclient.o
> -Wl,-fstack-protector-all -pthread  ./.libs/libcacard.so -lssl3
> -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lpthread -ldl
> -L/lib64 -lm -lgthread-2.0 -lglib-2.0 -lrt -lz -luuid -lutil
> -Wl,--rpath -Wl,/usr/local/lib
> /usr/bin/ld: -f may not be used without -shared

So the problem seems to be with "-Wl,-fstack-protector-all".  Where does
it come from?  QEMU or some pkg-config file?

Does it work if you configure with the --disable-stack-protector option?

Paolo