From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] paxtest: new package
Date: Sat, 22 Jul 2017 15:35:34 +0200 [thread overview]
Message-ID: <20170722153534.16f24300@windsurf> (raw)
In-Reply-To: <1499427897-36149-1-git-send-email-matthew.weber@rockwellcollins.com>
Hello,
On Fri, 7 Jul 2017 06:44:57 -0500, Matt Weber wrote:
> PaX regression test suite
>
> Signed-off-by: David Graziano <david.graziano@rockwellcollins.com>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
> ---
> Changes v2 -> v3
> [Arnout V
> - Add Config.in comment when glibc toolchain not used
> - Removed PAXTEST_SOURCE assignment as it was default
> - Updated ARMv# patch to be anything less then v7 instead of
> a range from 4-7
> - Tested that TARGET_CONFIGURE_OPTS could be used and added it in
> - Updated LD= to use TARGET_CC and enclosed in quotes
Applied to master, thanks. However, I have to say I very much dislike
the fact that a bunch of executable programs are installed right
into /usr/lib and not /usr/lib/paxtest or something like that. But
apparently RUNDIR is used to install both an actual shared library
(which must be in /usr/lib) and those executable programs.
Perhaps we could set RUNDIR=/usr/lib/paxtest, and as a post install
hook, move the single shared library being installed back
into /usr/lib ?
Could you test doing this ?
Since I've applied the patch, it should obviously be done by follow-up
patches, based on the latest master.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-22 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 11:44 [Buildroot] [PATCH v3 1/1] paxtest: new package Matt Weber
2017-07-22 0:02 ` Matthew Weber
2017-07-22 13:35 ` Thomas Petazzoni [this message]
2017-07-22 21:42 ` Matthew Weber
2017-07-23 2:03 ` Matthew Weber
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=20170722153534.16f24300@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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