Michael Matz wrote:
Hi,
On Thu, 10 May 2012, grischka wrote:
[1] See commit 27a428cd0fae475d7377e1dbe218c064ee217d85
Basically /usr/bin/env tcc -run will try to find tcc -run which is
then obviously not found. Should we go back to the solution proposed
in [2] or do you have another idea?
Greetings everybody,
I've just realized that the env trick to use tcc from the correct place [1]
doesn't work because neither Linux nor env split arguments at spaces.
[1] See commit 27a428cd0fae475d7377e1dbe218c064ee217d85
Basically /usr/bin/env tcc -run will try to find tcc -run which is then
Le jeudi 10 mai 2012 15:50:00, Thomas Preud'homme a écrit :
Greetings everybody,
I've just realized that the env trick to use tcc from the correct place [1]
doesn't work because neither Linux nor env split arguments at spaces.
[1] See commit 27a428cd0fae475d7377e1dbe218c064ee217d85
Couldn't we just create the binary called tcc-run, so users could say
#!/usr/bin/env tcc-run
at the top of their files?
On Thu, May 10, 2012 at 8:53 AM, Thomas Preud'homme robo...@celest.frwrote:
Le jeudi 10 mai 2012 15:50:00, Thomas Preud'homme a écrit :
Greetings everybody,
I've just
Thomas Preud'homme wrote:
Greetings everybody,
I've just realized that the env trick to use tcc from the correct place [1]
doesn't work because neither Linux nor env split arguments at spaces.
[1] See commit 27a428cd0fae475d7377e1dbe218c064ee217d85
Basically /usr/bin/env tcc -run will try
Hi,
On Thu, 10 May 2012, grischka wrote:
[1] See commit 27a428cd0fae475d7377e1dbe218c064ee217d85
Basically /usr/bin/env tcc -run will try to find tcc -run which is then
obviously not found. Should we go back to the solution proposed in [2] or
do you have another idea?
Why not use just
