public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/elfix:master commit in: misc/fix-gnustack/tests/
Date: Tue, 10 Jan 2023 05:21:41 +0000 (UTC)	[thread overview]
Message-ID: <1673328099.4fb8a9cb2a5410aa565d028bd8deb53d8682da62.sam@gentoo> (raw)

commit:     4fb8a9cb2a5410aa565d028bd8deb53d8682da62
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jan  6 05:39:13 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jan 10 05:21:39 2023 +0000
URL:        https://gitweb.gentoo.org/proj/elfix.git/commit/?id=4fb8a9cb

fix-gnustack: respect CFLAGS, LDFLAGS for tests

Needed to correctly run tests with Clang, as Clang doesn't create
executable stacks by default.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 misc/fix-gnustack/tests/Makefile.am | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/misc/fix-gnustack/tests/Makefile.am b/misc/fix-gnustack/tests/Makefile.am
index 9db0fd7..ad573a3 100644
--- a/misc/fix-gnustack/tests/Makefile.am
+++ b/misc/fix-gnustack/tests/Makefile.am
@@ -5,11 +5,11 @@ noinst_PROGRAMS = bad-gnustack
 EXTRA_DIST = gnustacktest.sh
 
 bad-gnustack.s: bad-gnustack.c
-	$(CC) -S $<
+	$(CC) $(CPPFLAGS) $(CFLAGS) -S $<
 	$(SED) -i -e 's/GNU-stack,"",/GNU-stack,"x",/' $@
 
 bad-gnustack$(EXEEXT): bad-gnustack.s
-	$(CC) -o $@ $<
+	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $<
 
 check_SCRIPTS = gnustacktest
 TEST = $(check_SCRIPTS)


             reply	other threads:[~2023-01-10  5:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  5:21 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-10  5:21 [gentoo-commits] proj/elfix:master commit in: misc/fix-gnustack/tests/ Sam James
2023-01-11  7:54 Sam James

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=1673328099.4fb8a9cb2a5410aa565d028bd8deb53d8682da62.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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