Bootstrap script

Ralf Corsepius ralf.corsepius at
Mon Apr 14 04:27:10 UTC 2008

On Mon, 2008-04-14 at 15:46 +1200, Nigel Spon wrote:
> If I do bootstrap -p in my BSP directory, I get:
> find: illegal option -- n
> find: illegal option -- a
> find: illegal option -- m
> find: illegal option -- e
> Generating ./
> This is apparently because the line:
> confs=`find -name -exec grep -l 'include .*/preinstall 
> \.am' {} \;`
> should be:
> confs=`find . -name -exec grep -l 'include .*/preinstall 
> \.am' {} \;`
> Is MacOSX being unusually fussy here?
Hmm, your report somewhat confuses me.

Though "find" has always been a portability problem (Hardly anything
about using find is portable), this particular construct is in bootstrap
for several years, without having seen any complaint by anybody else
before :(

Anyway, you seem to be saying that your "find" on MacOSX does not accept
an empty path argument.

This would correspond to POSIX, which says:
find [-H | -L] path ... [operand_expression ...]

=> Yes, it's very likely that MacOS's find is more fuzzy than other
other "find"s. 

Very odd about this: I have never seen such kind of behavior on any OS
before and there have even been MacOS users who reported to successfully
having used it.

* What does MacOSX's "man find" say?

* Which "find" is it?

[Please check the output of:
which find
type -p find
find --version

* Which shell are you using?

* Do you have white spaces or special characters in $PATH, cwd, 
or $HOME?

* Do you have any POSIX_* compatibility or similar environment variables

* Which version of MacOS X is it?


More information about the users mailing list