|Subject:||Re: [Tinycc-devel] tcc port to cygwin|
|Date:||Sun, 22 May 2016 16:56:20 -0400|
|User-agent:||Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0|
First, I would like to apologize for my random speculation that the bcheck.c compile problems from my posix cygwin port was a possible bug in tcc. Now that I'm further up the learning curve on tcc/compiling I think the most likely issue is include file compatability which results in invalid code getting to the tcc parsing routines. I did not mean to insult the active development effort that continues to improve tcc features and performance.
Second, what would be the best way (when, where, how...) to get the cygwin work into tcc upstream? I've sort of assumed that the mob branch is the true master from the activity on the mailing list. Is that true? In the meantime, I plan to set up a mirror on my github so that I can stand up a separate branch for the cygwin work for other developers to access in the meantime.
Third, any suggestions on how to diagnose and debug the problems of the cygwin system includes for gcc to use as simply as possible with tcc compilation?
On 5/20/2016 11:10, Chris Marshall wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|