[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] env executable examples

From: Thomas Preud'homme
Subject: Re: [Tinycc-devel] env executable examples
Date: Thu, 10 May 2012 15:53:24 +0200
User-agent: KMail/1.13.7 (Linux/3.2.0-2-amd64; KDE/4.7.4; x86_64; ; )

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
> 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?
> [2] cb2138f8b098feb1b51a407343a4b99e25d5b506
> Best regards,
> Thomas Preud'homme

Actually I've just realized another solution would be to search for a shebang 
to tcc when there is only one parameter and this is a c file.

This way we could do /usr/bin/env tcc and tcc would know it must run the 
TCC_OUTPUT_MEMORY option. The problem would then be that a file starting with a 
valid shebang could not be compiled & linked with tcc. It would break 
potential script doing tcc $file && ./a.out

What do you think?

Best regards,

Thomas Preud'homme

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]