On 14/10/11 16:04, Greg Troxel wrote: > I did get the following complaints when building: > > => Checking for non-existent script interpreters in tahoe-lafs-1.9.0b1 > WARNING: [check-interpreter.mk] The interpreter "/usr/bin/env" of > "[...]/allmydata/test/check_grid.py" is not allowed. > WARNING: [check-interpreter.mk] The interpreter "/usr/bin/env" of > "[...]/allmydata/test/check_load.py" is not allowed. > WARNING: [check-interpreter.mk] The interpreter "/usr/bin/env" of > "[...]/allmydata/test/check_memory.py" is not allowed. > WARNING: [check-interpreter.mk] The interpreter "/usr/bin/env" of > "[...]/allmydata/test/check_speed.py" is not allowed. > WARNING: [check-interpreter.mk] The interpreter "/usr/bin/env" of > "[...]/allmydata/test/test_base62.py" is not allowed. > WARNING: [check-interpreter.mk] The interpreter "/usr/bin/env" of > "[...]/allmydata/util/base62.py" is not allowed. > > The issue is that scripts that invoke python have to bind to the > specific version found at configure time and explicitly depended on. I > am not clear on how (or if) the tahoe build process deals with this, or > if I should treat it as a not-fixed upstream bug and patch it in pkgsrc.
I'd be happy with just removing the '#!/usr/bin/env python' lines and requiring these to be run explicitly via 'python'. -- David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
