On 06/06/2012 04:03 AM, Avi Kivity wrote:
Fedora 17's toolchain wants optimization enabled for _FORTIFY_SOURCE;
so disable _FORTIFY_SOURCE when debugging.
Signed-off-by: Avi Kivitya...@redhat.com
Applied. Thanks.
Regards,
Anthony Liguori
---
configure |3 +--
1 file changed, 1
On Wed, Jun 06, 2012 at 12:03:18PM +0300, Avi Kivity wrote:
Fedora 17's toolchain wants optimization enabled for _FORTIFY_SOURCE;
so disable _FORTIFY_SOURCE when debugging.
Signed-off-by: Avi Kivity a...@redhat.com
I was bitten by this problem too. The patch fixes it for me.
Tested-by:
Fedora 17's toolchain wants optimization enabled for _FORTIFY_SOURCE;
so disable _FORTIFY_SOURCE when debugging.
Signed-off-by: Avi Kivity a...@redhat.com
---
configure |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/configure b/configure
index 1f338f8..88d9c5b 100755
On 6 June 2012 10:03, Avi Kivity a...@redhat.com wrote:
Fedora 17's toolchain wants optimization enabled for _FORTIFY_SOURCE;
so disable _FORTIFY_SOURCE when debugging.
Well, that sucks, but it seems to be a deliberate change in
upstream glibc to make it warn now :-( I guess everybody
in the
