On Sun, Dec 27, 2009 at 06:45:14PM +0100, John Mandereau wrote:
> > It still needs the $(PYTHON), regardless wether it's in scripts/auxiliar
> > or scripts/build.
>
> For build scripts, the $(PYTHON) is put into the shebang when writing
> the script (and makeing it executable) from scripts/build t
Le dimanche 27 décembre 2009 à 18:30 +0100, Matthias Kilian a écrit :
> It still needs the $(PYTHON), regardless wether it's in scripts/auxiliar
> or scripts/build.
For build scripts, the $(PYTHON) is put into the shebang when writing
the script (and makeing it executable) from scripts/build to
sc
On Sun, Dec 27, 2009 at 06:09:15PM +0100, John Mandereau wrote:
> > - $(auxscript-dir)/yyout2grammar.py $(outdir)/parser.output $@
> > + $(PYTHON) $(auxscript-dir)/yyout2grammar.py $(outdir)/parser.output $@
>
> Oops, this script should be in scripts/build, not scripts/auxiliar, but
> this is
Le dimanche 27 décembre 2009 à 16:53 +0100, Matthias Kilian a écrit :
> The often-used idiom #!/usr/bin/env python not only is potentially
> dangerous, but it also fails if there are several versions of python
> installed, with the python binaries named python2.4, python2.5,
> python2.6, ...
>
> T
The often-used idiom #!/usr/bin/env python not only is potentially
dangerous, but it also fails if there are several versions of python
installed, with the python binaries named python2.4, python2.5,
python2.6, ...
This patch hopefully catches all remaining cases of a missing $(PYTHON).
---
Docum
