search for: take1

...> $@ || ( rm -f $@ ; exit 1 ) && \ >> chmod a+x $@ >> $(obj)/$(KLIBCCROSS)klcc: $(src)/makeklcc.pl $(src)/klcc.in \ This doesn't work with older versions of make. ?make 4.2.1 seems common now and does not support $(shell command). $ cat Makefile $(info take1: $(shell command -v ls)) $(info take2: $(shell bash -c 'type -p ls')) all: @true $ make-3.81/make make: command: Command not found take1: take2: /bin/ls $ make-4.2.1/make make: command: Command not found take1: take2: /bin/ls $ make-4.3/make take1: /bin/ls take2: /bin/ls https:...

Currently, in the entire klibc bash is only used to identify the path of the perl binary. It is doing so using the bash built-in 'type' function, which is POSIX compliant according to [0], but the option -c is not. By using `command -v` instead, we achieve the same result, in a POSIX compliant manor [1], potentially removing the unneeded bash dependency. 0

Greg Thelen dixit: >This doesn't work with older versions of make. ?make 4.2.1 seems common >now and does not support $(shell command). > >$ cat Makefile >$(info take1: $(shell command -v ls)) >$(info take2: $(shell bash -c 'type -p ls')) > >all: > @true > >$ make-3.81/make >make: command: Command not found Eh, what? ? checks with gmake 3.81? indeed. But no, this isn?t correct. You just do this instead: $(info take1: $(shel...

Hey Greg, On 08-09-2020 22:07, Thorsten Glaser wrote: > Greg Thelen dixit: > >> This doesn't work with older versions of make. ?make 4.2.1 seems common >> now and does not support $(shell command). >> >> $ cat Makefile >> $(info take1: $(shell command -v ls)) >> $(info take2: $(shell bash -c 'type -p ls')) >> >> all: >> @true >> >> $ make-3.81/make >> make: command: Command not found > > Eh, what? well command can be either a shell built-in or an external program,...