> ifdef CONFIG_WIN32 > TCCFLAGS = -B$(top_srcdir)/win32 -I$(top_srcdir)
> -I$(top_srcdir)/include -L$(TOP) > endif
And where the case of CONFIG_WIN64?
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinyc
you changed the code to use 'realpath', but realpath is not available
on all systems.
old code can be used for suçh systems. I don't like to use cp on Linux.
PS: I currently on tablet, a notebook must be repaired.
2016-05-20 18:29 GMT+03:00, avih :
> @seyko
> While I appreciate the confidence i
Subject: Re: [Tinycc-devel] tcc compilation on MSYS2
> The mob branch does not have tests/exsymtab/* which your updated configure
tries to use.
my fault. please fix it (I can't now)
> You didn't take my change at tests/Makefile, and without this change it
won't work on wind
> The mob branch does not have tests/exsymtab/* which your updated configure
> tries to use.
my fault. please fix it (I can't now)
> You didn't take my change at tests/Makefile, and without this change it won't
> work on windows (It needs -I$(TOP) because the configured config.h is there
> and
> The mob branch does not have tests/exsymtab/* which your updated configure
> tries to use.
my fault. please fix it (I can't now)
> You didn't take my change at tests/Makefile, and without this change it won't
> work on windows (It needs -I$(TOP) because the configured config.h is there
> and
@seyko
While I appreciate the confidence in me when you take code/patches which I
wrote and commit them to mob yourself (and also the credit which you gave in
your commits from today - in the past you did so without giving credit IIRC),
I'd also appreciate some heads up and possibly some discuss
Hey Chris,
The latest tcc work is in the mob branch, and there have been preprocessor
fixes in there recently. You should definitely work off of that branch.
David
On Thu, May 19, 2016 at 2:10 PM, Chris Marshall
wrote:
> It looks like this is definitely a bug in the version of tcc git I have.
It looks like this is definitely a bug in the version of tcc git I have.
At least the error message I'm getting in the code does not appear
to be possible since the error call is from skip() but there are no
calls to skip() that could have the ')' as reported in the error so
something is off-by-one
Is it possible that this could be a bug in the tcc preprocessing?
On Thu, May 19, 2016 at 10:33 AM, Chris Marshall
wrote:
> Thanks for the help.
>
> I've got tcc building but the bcheck.c compile is failing
> when the stdlib.h is pulled in. My next step is to try
> the same with the latest tcc
Thanks for the help.
I've got tcc building but the bcheck.c compile is failing
when the stdlib.h is pulled in. My next step is to try
the same with the latest tcc git. I'm not sure what the
best way to proceed woud be. The top level gcc build
can correctly (for cygwin) process the various syste
Maybe it would be better to have tcc define (or not) TCC_BCHECK, and then this
file, and possibly elsewhere too, check only this instead of all these tests?
On Wednesday, May 18, 2016 7:31 AM, Sergey Korshunoff
wrote:
> However, since the
> preprocessing is being done by tcc the __CYGW
> However, since the
> preprocessing is being done by tcc the __CYGWIN__ macro is not defined
> and I can't figure out where that would go.
iff --git a/libtcc.c b/libtcc.c
index 7d9a058..a5ec7f3 100644
--- a/libtcc.c
+++ b/libtcc.c
@@ -1170,6 +1170,8 @@ LIBTCCAPI TCCState *tcc_new(void)
# ifdef TC
I don't mean exactly the same code but since cygwin is a flavor of posix
system,
it should be possible to support it the way that MacOSX, linux, and *bsd
are.
@David: ./configure works out of the box.
make goes well until it hits tccrun.c where there is no appropriate version
of rt_get_caller_pc()
Adding in a case in the re_get_caller_pc() code for defined(__CYGWIN__)
like:
#elif defined(__CYGWIN__)
*paddr = uc->uc_mcontext.eip;
for each of the 4 cases allowed this to compile. Then there were some
issues
with stdint.h failing in the libtcc.c compile because on cygwin, the
stdint
> I'm trying to do that, i.e MSYS2 unix.
Fixed a mingw64 build on Linux with --enable-tcc64-mingw
https://github.com/seyko2/tinycc/commit/47f80bd7f70904711a046c4ca98de2657ad298a7
Problem: a name of the libtcc.a and libtcc1.a libraries is the same
for 32 and 64 builds. And all files go to the C:\Pr
@avih
> apparently there have been some build system changed between December and now
yes, the same is on my branch. A problem is exposed after my commit
commit 7ed43415380ec6270e53c0ed3f42e5cb99df1f6e
Author: seyko bad
Date: Wed Mar 4 10:57:13 2015 +0
On Sat, May 14, 2016 at 3:27 PM, grischka wrote:
> Chris Marshall wrote: ---
>
>> To be more specific, it should be possible to build the mingw version of
>> tcc on cygwin (I don't know, haven't had time to try) but what I would like
>> is the linux/unix version---if it builds on unix, it should
Chris Marshall wrote: ---
To be more specific, it should be possible to build the mingw version of
tcc on cygwin (I don't know, haven't had time to try) but what I would
like is the linux/unix version---if it builds on unix, it should be
buildable on cygwin---as long as you don't look under the
> You can try my branch: https://github.com/avih/tinycc/commits/drafts (note, I
> force-push and keep it rebased on top of mob).
First impression with this branch on Linux:
1)
fantoo tinycc # ./configure
Binary directory /usr/local/bin
TinyCC directory/usr/local/lib/tcc
Library directory
> You can try my branch: https://github.com/avih/tinycc/commits/drafts (note, I
> force-push and keep it rebased on top of mob).
>I wanted to push some/all of the commits on my "drafts" branch to mob after
>some cleanups, but never really got to end up doing it. If there's enough
>interest and
To be more specific, it should be possible to build the mingw version of
tcc on cygwin (I don't know, haven't had time to try) but what I would
like is the linux/unix version---if it builds on unix, it should be
buildable on cygwin---as long as you don't look under the covers to find
windows.
Hello Sergey,
Is this an issue with the standard Makefile, or with the Windows-specific
build batch (.BAT) file? FWIW, the batch file build-process works in at
least some of the mingw setups provided by Strawberry Perl.
David
On Sat, May 14, 2016 at 3:24 AM, Sergey Korshunoff wrote:
> MSYS2 is
As someone whose primary development environment is cygwin/win7, I would
love for tcc to build and run under cygwin.
--Chris
On 5/14/2016 03:24, Sergey Korshunoff wrote:
MSYS2 is current environment for Qt and other software development on
Windows. It is a mingw+cygwin with a package manager
MSYS2 is current environment for Qt and other software development on
Windows. It is a mingw+cygwin with a package manager (pacman), ported
from ARCH Linux. MSYS2 allow to build
mingw32/mingw64/cygwin32/cygwin64 programs in unix-like environment.
Currenly tcc can not be build on this environment (m
24 matches
Mail list logo
