From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] e2fsprogs: 1.43 -> 1.43.1
Date: Tue, 12 Jul 2016 19:46:18 +0800 [thread overview]
Message-ID: <5784D88A.4080101@windriver.com> (raw)
In-Reply-To: <CAJTo0LaRh6d67+eKrcGA2fQSxeR06-xQd7tB7xs_4_kx4FRakw@mail.gmail.com>
On 07/07/2016 05:53 PM, Burton, Ross wrote:
>
> On 7 July 2016 at 08:54, Andre McCurdy <armccurdy@gmail.com
> <mailto:armccurdy@gmail.com>> wrote:
>
> Based on the e2fsprogs release notes, v1.43.1 adds a new configure
> option, --enable-hardening
>
> http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.43.1
>
> It might be nice to either enable that by default, or provide a
> PACKAGECONFIG to control it (and in either case, verify that it
> doesn't conflict with security_flags.inc).
>
>
> I'd lean toward enabling by default and then nullifying security_flags, assuming
> that the latter is effectively the same as the former, considering that the
> flags are supported upstream.
Hi Ross,
I updated it in the repo, enable it by default for target, it can't build
with native:
| checking for uuid_generate in -luuid... no
| configure: error: external uuid library not found
And "require conf/distro/include/security_flags.inc" doesn't affect the
build result.
git://git.openembedded.org/openembedded-core-contrib rbt/pu
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/pu
Robert Yang (7):
debianutils: 4.7 -> 4.8
e2fsprogs: 1.43 -> 1.43.1
git: 2.8.4 -> 2.9.0
gmp: 6.1.0 -> 6.1.1
libpcre: 8.38 -> 8.39
wget: 1.17.1 -> 1.18
file: 5.27 -> 5.28
// Robert
>
> Ross
next prev parent reply other threads:[~2016-07-12 11:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 1:36 [PATCH 0/7] Packages Upgrade Robert Yang
2016-07-07 1:37 ` [PATCH 1/7] debianutils: 4.7 -> 4.8 Robert Yang
2016-07-07 1:37 ` [PATCH 2/7] e2fsprogs: 1.43 -> 1.43.1 Robert Yang
2016-07-07 7:54 ` Andre McCurdy
2016-07-07 9:53 ` Burton, Ross
2016-07-12 11:46 ` Robert Yang [this message]
2016-07-07 1:37 ` [PATCH 3/7] git: 2.8.4 -> 2.9.0 Robert Yang
2016-07-07 13:14 ` Dan McGregor
2016-07-11 21:11 ` Burton, Ross
2016-07-12 12:05 ` Robert Yang
2016-07-07 1:37 ` [PATCH 4/7] gmp: 6.1.0 -> 6.1.1 Robert Yang
2016-07-07 1:37 ` [PATCH 5/7] libpcre: 8.38 -> 8.39 Robert Yang
2016-07-07 1:37 ` [PATCH 6/7] wget: 1.17.1 -> 1.18 Robert Yang
2016-07-07 1:37 ` [PATCH 7/7] file: 5.27 -> 5.28 Robert Yang
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=5784D88A.4080101@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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