From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] paxtest: new package
Date: Wed, 21 Jun 2017 22:29:39 +0200 [thread overview]
Message-ID: <20170621222939.2f43e719@windsurf> (raw)
In-Reply-To: <1497906876-27014-1-git-send-email-matthew.weber@rockwellcollins.com>
Hello,
Thanks for this contribution. A few comments below. Could you address
them, and send an updated version? Thanks!
On Mon, 19 Jun 2017 16:14:36 -0500, Matt Weber wrote:
> package/Config.in | 1 +
> .../0001-genpaxtest-move-log-location.patch | 54 ++++++++++++++++++++++
> package/paxtest/Config.in | 5 ++
> package/paxtest/paxtest.hash | 2 +
> package/paxtest/paxtest.mk | 30 ++++++++++++
Missing entry in DEVELOPERS file.
> diff --git a/package/paxtest/0001-genpaxtest-move-log-location.patch b/package/paxtest/0001-genpaxtest-move-log-location.patch
> new file mode 100644
> index 0000000..9fc898d
> --- /dev/null
> +++ b/package/paxtest/0001-genpaxtest-move-log-location.patch
> @@ -0,0 +1,54 @@
> +From 623d99e4f557ef9cd771006e4f916c12d22a07a8 Mon Sep 17 00:00:00 2001
> +From: David Graziano <david.graziano@rockwellcollins.com>
> +Date: Mon, 12 Jun 2017 10:41:45 -0500
> +Subject: [PATCH] genpaxtest: move log location
> +
> +Move log location to /tmp instead of local directory.
> +(For read-only filesystems)
Is /tmp really the right place? What about /var/log instead?
> diff --git a/package/paxtest/Config.in b/package/paxtest/Config.in
> new file mode 100644
> index 0000000..f5ed60d
> --- /dev/null
> +++ b/package/paxtest/Config.in
> @@ -0,0 +1,5 @@
> +config BR2_PACKAGE_PAXTEST
> + bool "paxtest"
> + depends on BR2_TOOLCHAIN_USES_GLIBC
Could you please add a comment about why we have this glibc dependency?
> + help
> + PaX regression test suite
Please add a blank line, followed by the upstream URL of the project.
And also a Config.in comment about the glibc dependency.
> +PAXTEST_VERSION = 0.9.11
> +PAXTEST_SOURCE = paxtest_$(PAXTEST_VERSION).orig.tar.gz
> +PAXTEST_SITE = http://http.debian.net/debian/pool/main/p/paxtest
What about using the latest version, 0.9.15, available at
https://www.grsecurity.net/~spender/paxtest-0.9.15.tar.gz. It is the
one used by Gentoo, for example.
> +PAXTEST_LICENSE = GPL-2.0+
> +PAXTEST_LICENSE_FILES = README
> +
> +PAXTEST_MAKE_OPTS = \
> + CC=$(TARGET_CC) \
> + LD=$(TARGET_LD)
Is it possible to use $(TARGET_CONFIGURE_OPTS) instead?
> +
> +PAXTEST_INSTALL_TARGET_OPTS = \
> + DESTDIR=$(TARGET_DIR) \
> + BINDIR="usr/bin" \
> + RUNDIR="usr/lib"
Both PAXTEST_MAKE_OPTS and PAXTEST_INSTALL_TARGET_OPTS are used only
once, so don't define variable: just use them directly where needed.
> +
> +define PAXTEST_BUILD_CMDS
> + $(MAKE) -C $(@D) $(PAXTEST_MAKE_OPTS) linux
Please pass $(TARGET_MAKE_ENV) before $(MAKE).
> +endef
> +
> +define PAXTEST_INSTALL_TARGET_CMDS
> + $(MAKE) -C $(@D) -f Makefile.psm install $(PAXTEST_INSTALL_TARGET_OPTS)
Ditto.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-21 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 21:14 [Buildroot] [PATCH 1/1] paxtest: new package Matt Weber
2017-06-21 20:29 ` Thomas Petazzoni [this message]
2017-06-22 12:50 ` Matthew Weber
2017-07-05 21:47 ` 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=20170621222939.2f43e719@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 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.