Makefile assumes /usr/bin/python
Bug #305231 reported by
Adam K Kirchhoff
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Universal Applets |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
Line 23 specifies a full path for python, and assumes it's /usr/bin. This is not the case for FreeBSD (or, really, on any system where python is manually installed by a user). The lines that just use 'python' without a full path work just fine. Frankly, I think the best idea would be to use 'env python'.
Adam
To post a comment you must log in.
I'm assuming you meant universal- applets- extras here.
I assume that when "python" is called in a Makefile, the shell scans the user's $PATH and uses the first instance.
Is there any advantage of using /usr/bin/env over this? (I know about using it in shell scripts, but not in Makefiles)
Whichever we use, it should be consistent in both extras and core.