Re: [gpsd-dev] build.txt does not explain python path

[Eric S. Raymond]

Greg Troxel <address@hidden>:
> On a system with /usr/pkg/bin/python2.7 but no "python", all the tests
> failed, even though I had PYTHON=/usr/pkg/bin/python2.7 in the
> environment to scons.  build.txt doesn't explain how to pass in a path
> (or I didn't find it by skimming or grepping).  And, scons didn't find
> it, even though python2.7 was in PATH.

Oh, bletch.

Several Python scripts (including gpsfake) have the notion that 'python' 
will get them Python wired in to #! header.  That's why your tests failed.

This will be messy to fix.  In the meantime, I suggest creating a python
symlink in your ~/bin.  I'll add a note about this to build.txt.
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>

signature.asc
Description: Digital signature