Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

find: unrecognized: -execdir PR buildconf: use find -execdir / busybox find #5483

Closed
MaxPeal opened this issue May 29, 2020 · 4 comments
Closed
Labels

Comments

@MaxPeal
Copy link

MaxPeal commented May 29, 2020

after the commit (c712009)

the build fails and/or generate lots of errors.
as the busybox find dont support -execdir
travis build errors

With these errors: the travis runs should show an error message, shouldn't they?

@MaxPeal
Copy link
Author

MaxPeal commented May 29, 2020

form the logs:
...
buildconf: GNU m4 version 1.4.18 (ok)

find: unrecognized: -execdir

BusyBox v1.31.1 () multi-call binary.

Usage: find [-HL] [PATH]... [OPTIONS] [ACTIONS]

Search for files and perform actions on them.

First failed action stops processing of current file.

Defaults: PATH is current directory, action is '-print'

-L,-follow	Follow symlinks

-H		...on command line only

-xdev		Don't descend directories on other filesystems

-maxdepth N	Descend at most N levels. -maxdepth 0 applies

		actions to command line arguments only

-mindepth N	Don't act on first N levels

-depth		Act on directory *after* traversing it

Actions:

( ACTIONS )	Group actions for -o / -a

! ACT		Invert ACT's success/failure

ACT1 [-a] ACT2	If ACT1 fails, stop, else do ACT2

ACT1 -o ACT2	If ACT1 succeeds, stop, else do ACT2

		Note: -a has higher priority than -o

-name PATTERN	Match file name (w/o directory name) to PATTERN

-iname PATTERN	Case insensitive -name

-path PATTERN	Match path to PATTERN

-ipath PATTERN	Case insensitive -path

-regex PATTERN	Match path to regex PATTERN

-type X		File type is X (one of: f,d,l,b,c,s,p)

-executable	File is executable

-perm MASK	At least one mask bit (+MASK), all bits (-MASK),

		or exactly MASK bits are set in file's mode

-mtime DAYS	mtime is greater than (+N), less than (-N),

		or exactly N days in the past

-mmin MINS	mtime is greater than (+N), less than (-N),

		or exactly N minutes in the past

-newer FILE	mtime is more recent than FILE's

-inum N		File has inode number N

-user NAME/ID	File is owned by given user

-group NAME/ID	File is owned by given group

-size N[bck]	File size is N (c:bytes,k:kbytes,b:512 bytes(def.))

		+/-N: file size is bigger/smaller than N

-links N	Number of links is greater than (+N), less than (-N),

		or exactly N

-prune		If current file is directory, don't descend into it

If none of the following actions is specified, -print is assumed

-print		Print file name

-print0		Print file name, NUL terminated

-exec CMD ARG ;	Run CMD with all instances of {} replaced by

		file name. Fails if CMD exits with nonzero

-exec CMD ARG + Run CMD with {} replaced by list of file names

-delete		Delete current file/directory. Turns on -depth option

-quit		Exit

find: unrecognized: -execdir

BusyBox v1.31.1 () multi-call binary.
...

@bagder
Copy link
Member

bagder commented May 29, 2020

Can you just check? No, travis shows no errors. Presumably it doesn't use busybox's find. I don't understand why someone would do that for development.

@bagder
Copy link
Member

bagder commented May 29, 2020

In most cases that is a fairly benign problem too.

@bagder bagder added the build label May 29, 2020
@MaxPeal
Copy link
Author

MaxPeal commented May 29, 2020

with a manual make build with/in the curl-docker its the same problem

bagder added a commit that referenced this issue May 29, 2020
…res files"

This partially reverts commit c712009.

Keep the ares_ files removed but bring back the older way to run find,
to make it work with busybox's find, as apparently that's being used.

Reported-by: Max Peal
Fixes #5483
@bagder bagder closed this as completed in d618986 May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.

2 participants