From: Uqbar <1660599@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1660599] [NEW] v2.8.0 won't compile if g++ compiler doesn't understand "-fstack-protector-strong"
Date: Tue, 31 Jan 2017 11:45:43 -0000 [thread overview]
Message-ID: <20170131114543.27337.90403.malonedeb@wampee.canonical.com> (raw)
Public bug reported:
For example, Ubuntu Trusty (LTS 14.04) uses g++ v4.8.5.
Compilation fails with a syntax error saying that the ""-fstack-protector-strong" option in g++ is unrecognized.
Instead, under Ubuntu Xenial (LTS 16.04), the g++ compiler is v5.4.0 and the compilation goes on smoothly.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1660599
Title:
v2.8.0 won't compile if g++ compiler doesn't understand "-fstack-
protector-strong"
Status in QEMU:
New
Bug description:
For example, Ubuntu Trusty (LTS 14.04) uses g++ v4.8.5.
Compilation fails with a syntax error saying that the ""-fstack-protector-strong" option in g++ is unrecognized.
Instead, under Ubuntu Xenial (LTS 16.04), the g++ compiler is v5.4.0 and the compilation goes on smoothly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1660599/+subscriptions
next reply other threads:[~2017-01-31 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 11:45 Uqbar [this message]
2017-03-26 10:20 ` [Qemu-devel] [Bug 1660599] Re: v2.8.0 won't compile if g++ compiler doesn't understand "-fstack-protector-strong" Danil
2018-04-26 10:28 ` Thomas Huth
2018-06-26 4:17 ` Launchpad Bug Tracker
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=20170131114543.27337.90403.malonedeb@wampee.canonical.com \
--to=1660599@bugs.launchpad.net \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.