From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [morty][PATCH 0/1] packagegroup-core-standalone-sdk-target: add libssp
Date: Fri, 7 Apr 2017 14:38:12 +1200 [thread overview]
Message-ID: <cover.1491532173.git.paul.eggleton@linux.intel.com> (raw)
Backport this to morty since if you want runtime support for stack-smashing
protection when building with gcc you need this library.
The following changes since commit ddf907ca95a19f54785079b4396935273b3747f6:
Revert "file: update SRCREV for 5.28 to fix fetch fail on missing commit" (2017-03-21 22:17:57 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/libssp-sdk-morty
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/libssp-sdk-morty
Paul Eggleton (1):
packagegroup-core-standalone-sdk-target: add libssp
.../packagegroups/packagegroup-core-standalone-sdk-target.bb | 5 +++++
1 file changed, 5 insertions(+)
--
2.9.3
next reply other threads:[~2017-04-07 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 2:38 Paul Eggleton [this message]
2017-04-07 2:38 ` [morty][PATCH 1/1] packagegroup-core-standalone-sdk-target: add libssp Paul Eggleton
2017-04-07 17:00 ` akuster808
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=cover.1491532173.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.