From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/nfs-utils/files/
Date: Sun, 5 Jan 2020 05:23:24 +0000 (UTC) [thread overview]
Message-ID: <1578201697.97e3aec5c63139c691c99a7d5fc1600fd8814e66.vapier@gentoo> (raw)
commit: 97e3aec5c63139c691c99a7d5fc1600fd8814e66
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 5 05:21:37 2020 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Sun Jan 5 05:21:37 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97e3aec5
net-fs/nfs-utils: add metadata to cross-compile patch
Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>
.../nfs-utils/files/nfs-utils-1.2.8-cross-build.patch | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/net-fs/nfs-utils/files/nfs-utils-1.2.8-cross-build.patch b/net-fs/nfs-utils/files/nfs-utils-1.2.8-cross-build.patch
index 7317115a0e1..366a85badfe 100644
--- a/net-fs/nfs-utils/files/nfs-utils-1.2.8-cross-build.patch
+++ b/net-fs/nfs-utils/files/nfs-utils-1.2.8-cross-build.patch
@@ -3,6 +3,25 @@ for us atm, so hack away :(
(recent autotools will always add $(CFLAGS)/etc... to the compile)
+posted upstream:
+https://marc.info/?l=linux-nfs&m=136416341629788&w=2
+Date: Sun, 24 Mar 2013 22:21:08 +0000
+Message-ID: 1364163668-15490-1-git-send-email-vapier@gentoo.org
+
+From 269ae1346d9ccc97304205066d20e7e7b638f30e Mon Sep 17 00:00:00 2001
+From: Mike Frysinger <vapier@gentoo.org>
+Date: Sun, 24 Mar 2013 18:14:48 -0400
+Subject: [PATCH nfs-utils] locktes/rpcgen: tweak how we override compiler settings
+
+Newer autotools will use both CFLAGS and <target>_CFLAGS when compiling
+the <target>. Adding the build settings to the target-specific flags no
+longer works as a way to compile build-time tools.
+
+Instead, clobber the global flags. This triggers an automake warning,
+but the end result actually works (unlike the existing code).
+
+Signed-off-by: Mike Frysinger <vapier@gentoo.org>
+
--- a/tools/locktest/Makefile.am
+++ b/tools/locktest/Makefile.am
@@ -1,12 +1,11 @@
next reply other threads:[~2020-01-05 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 5:23 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 19:45 [gentoo-commits] repo/gentoo:master commit in: net-fs/nfs-utils/files/ Mike Gilbert
2022-09-26 12:10 Sam James
2021-04-11 15:49 David Seifert
2019-11-08 2:44 Aaron Bauman
2019-09-02 7:08 Matt Turner
2019-09-02 7:08 Matt Turner
2018-01-18 16:45 Mike Gilbert
2017-12-20 20:17 Thomas Deutschmann
2017-01-22 21:09 Robin H. Johnson
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=1578201697.97e3aec5c63139c691c99a7d5fc1600fd8814e66.vapier@gentoo \
--to=vapier@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