[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Use of non-portable find options in Makefile.in

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 3 Mar 2014 19:28:49 +0100

On Mon, Mar 03, 2014 at 05:34:22PM +0000, Philip Martin wrote:
> I've been experimenting with a SPARC Solaris build recently and the
> non-portable use of find in Makefile.in is annoying, it means that the
> 'make clean' target fails. There are two uses of
> find some/path -mindepth 1 -maxdepth 1 -print0 | xargs -0 rm -rf --
> Solaris find doesn't support -mindepth, -maxdepth or -print0.
> Are we using -print0 because problems with spaces in paths have been
> observed or simply as some sort of future-proofing? Don't we control
> the paths thus allowing us to avoid spaces?
> The use of -mindepth 1 -maxdepth 1 is also something I don't understand,

The first instance was added in r1421636, and the second one
copied from there in r1539215.

I agree that the Makefile should be as portable as possible
and support any of the alternatives you've mentioned.
Received on 2014-03-03 19:29:23 CET

This is an archived mail posted to the Subversion Dev mailing list.