[pkgsrc/trunk]: pkgsrc/meta-pkgs/boost boost: Use XARGS instead of -exec of F...

[leot <leot%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/ea778ab3df93
branches:  trunk
changeset: 384749:ea778ab3df93
user:      leot <leot%pkgsrc.org@localhost>
date:      Sun Sep 02 12:53:36 2018 +0000

description:
boost: Use XARGS instead of -exec of FIND to properly address PR pkg/53543

This should properly fix PR pkg/53543 (also remove the big `XXX'
comment, this is a proper solution to the problem).

Thanks to <joerg> for suggesting that!

diffstat:

 meta-pkgs/boost/Makefile.common |  8 ++------
 1 files changed, 2 insertions(+), 6 deletions(-)

diffs (23 lines):

diff -r 33d673d2effc -r ea778ab3df93 meta-pkgs/boost/Makefile.common
--- a/meta-pkgs/boost/Makefile.common   Sun Sep 02 12:52:12 2018 +0000
+++ b/meta-pkgs/boost/Makefile.common   Sun Sep 02 12:53:36 2018 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile.common,v 1.76 2018/09/01 21:21:46 leot Exp $
+# $NetBSD: Makefile.common,v 1.77 2018/09/02 12:53:36 leot Exp $
 #
 # used by devel/boost-build/Makefile
 # used by devel/boost-docs/Makefile
@@ -88,12 +88,8 @@
 
 # We can't do this at post-extract because the extract cookie will get a future
 # timestamp than the sources.  If this happens, print-PLIST does not work.
-#
-# XXX: As pointed out by PR pkg/53543 using `+' in ${FIND} can lead to
-# XXX: `Argument list too long' errors when building devel/boost-libs.
-# XXX: As a workaround use `\;' instead.
 pre-configure:
-       ${FIND} ${WRKSRC} -type f -exec ${TOUCH} {} \;
+       ${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH}
 
 # Generate a new user.hpp or use the installed one, depending on the package
 # we are building.