qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Hindin <jhindin@daynix.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: [Qemu-devel] Another solution for qga-vss stack protection issue
Date: Sun, 15 Mar 2015 17:35:25 +0200	[thread overview]
Message-ID: <1426433726-21414-1-git-send-email-jhindin@daynix.com> (raw)

qga/vss-win32/Makefile.objsi filters  out -fstack-protector-all option from C++ flags,
but with commit 63678e17c configure script may add option -fstack-protector-strong,
depending on availability. The suggested change filters out both option for qga-vss.dll
linking.

     Regards,
          Joseph Hindin

             reply	other threads:[~2015-03-15 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 15:35 Joseph Hindin [this message]
2015-03-15 15:35 ` [Qemu-devel] [PATCH] gemu-ga-win: configure script may add -fstack-protector-strong option instead of -fstack-protector-all, depending on availability ( see commit 63678e17c ). Both options have to by filtered out for qga-vss.dll Joseph Hindin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1426433726-21414-1-git-send-email-jhindin@daynix.com \
    --to=jhindin@daynix.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).