> I'd say that this patch looks more like someone's personal easter egg,> or at
> least you missed to explain why you would recommend other people
> to use an install structure as you do as well, what the benefit is over
> the one that they already have, and how they are supposed to create it,
>
> Where is this path allocation freed?When the program exits. It is allocated
> once at program startup, andthen auto-freed at program termination. But,
> sure, I could add a free.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
On 27.05.2023 02:28, Fred van Kempen via Tinycc-devel wrote:
Herman:
>> Based on the 0.9.27 release code, I added a patch to tcc.c to let it "find"
itself and its
>> support directories (include, lib etc) even it is not located in the root
of that setup. I
>> normally have stuff organized
: [Tinycc-devel] patch for tcc (and question)
Herman:
>> Based on the 0.9.27 release code, I added a patch to tcc.c to let it "find"
>> itself and its
>> support directories (include, lib etc) even it is not located in the root of
>> that setup. I
>>
Herman:
>> Based on the 0.9.27 release code, I added a patch to tcc.c to let it "find"
>> itself and its >> support directories (include, lib etc) even it is not
>> located in the root of that setup. I >> normally have stuff organized under
>> "bin/" to keep it clean, and because my systems >>
On 5/17/23 23:28, Fred van Kempen wrote:
Hello list:
I hope the list is still active... development seems to have stopped,
or at least stalled?
Based on the 0.9.27 release code, I added a patch to tcc.c to let it
"find" itself and its
support directories (include, lib etc) even it is not
