From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/liblockfile/files/
Date: Sat, 28 Nov 2020 00:52:23 +0000 (UTC) [thread overview]
Message-ID: <1606524740.a93170144777642a7878a0f2a27c6802a982b903.sam@gentoo> (raw)
commit: a93170144777642a7878a0f2a27c6802a982b903
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 28 00:52:10 2020 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 28 00:52:20 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9317014
net-libs/liblockfile: fix build failure
"lockfile.c:57:11: error: ‘LOCKPROG’ undeclared (first use in this function)"
Package-Manager: Portage-3.0.9, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-libs/liblockfile/files/Makefile.Darwin.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-libs/liblockfile/files/Makefile.Darwin.in b/net-libs/liblockfile/files/Makefile.Darwin.in
index bdd320fe6d4..936d48a2d1d 100644
--- a/net-libs/liblockfile/files/Makefile.Darwin.in
+++ b/net-libs/liblockfile/files/Makefile.Darwin.in
@@ -48,7 +48,7 @@ lockfile.o: lockfile.c
-c lockfile.c
xlockfile.o: lockfile.c
- $(CC) $(CFLAGS) -c lockfile.c -o xlockfile.o
+ $(CC) $(CFLAGS) -DLOCKPROG=\"$(bindir)/dotlockfile\" -c lockfile.c -o xlockfile.o
install_static: static install_common
install -m 644 liblockfile.a $(ROOT)$(libdir)
next reply other threads:[~2020-11-28 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 0:52 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-28 1:08 [gentoo-commits] repo/gentoo:master commit in: net-libs/liblockfile/files/ Sam James
2020-05-06 11:51 Joonas Niilola
2019-08-14 12:15 Guilherme Amadio
2017-09-15 5:45 Benda XU
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=1606524740.a93170144777642a7878a0f2a27c6802a982b903.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