From: Stephen Smalley <sds@tycho.nsa.gov>
To: Ondrej Mosnacek <omosnace@redhat.com>, selinux@vger.kernel.org
Subject: Re: [PATCH 2/2] Travis-CI: test that DEBUG build works
Date: Fri, 7 Feb 2020 16:27:57 -0500 [thread overview]
Message-ID: <6fd93c7d-e5fe-b5ce-d5cc-b11125b9c587@tycho.nsa.gov> (raw)
In-Reply-To: <20200206131901.535779-3-omosnace@redhat.com>
On 2/6/20 8:19 AM, Ondrej Mosnacek wrote:
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
> ---
> .travis.yml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.travis.yml b/.travis.yml
> index e9f86baa..918958ac 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -13,6 +13,7 @@ env:
> # Test the last version of Python and Ruby together, with some linkers
> - PYVER=python3.7 RUBYLIBVER=2.6
> - PYVER=python3.7 RUBYLIBVER=2.6 TEST_FLAGS_OVERRIDE=1
> + - PYVER=python3.7 RUBYLIBVER=2.6 TEST_DEBUG=1
> - PYVER=python3.7 RUBYLIBVER=2.6 LINKER=gold
> - PYVER=python3.7 RUBYLIBVER=2.6 LINKER=bfd
>
> @@ -116,6 +117,8 @@ before_script:
>
> # If TEST_FLAGS_OVERRIDE is defined, test that overriding CFLAGS, LDFLAGS and other variables works fine
> - if [ -n "$TEST_FLAGS_OVERRIDE" ]; then EXPLICIT_MAKE_VARS="CFLAGS=-I$DESTDIR/usr/include LDFLAGS=-L$DESTDIR/usr/lib LDLIBS= CPPFLAGS=" ; fi
> + # If TEST_DEBUG is defined, test that debug build works fine
> + - if [ -n "$TEST_DEBUG" ]; then EXPLICIT_MAKE_VARS="$EXPLICIT_MAKE_VARS DEBUG=1" ; fi
>
> script:
> # Start by installing everything into $DESTDIR
>
next prev parent reply other threads:[~2020-02-07 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 13:18 [PATCH 0/2] userspace: Fix DEBUG=1 build Ondrej Mosnacek
2020-02-06 13:19 ` [PATCH 1/2] libsemanage: preserve parent Makefile's flags in debug mode Ondrej Mosnacek
2020-02-06 13:19 ` [PATCH 2/2] Travis-CI: test that DEBUG build works Ondrej Mosnacek
2020-02-07 21:27 ` Stephen Smalley [this message]
2020-02-10 14:36 ` Stephen Smalley
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=6fd93c7d-e5fe-b5ce-d5cc-b11125b9c587@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).