Tiny C Compiler for Windows Source

[Werner Nussbaumer]

Hello

I am searching for a version of the Tiny C compiler for Windows 32. I
downloaded a version from http://fabrice.bellard.free.fr/tcc/ but the
make command displayed error messages:

P:\DEVELOP\c2\TCC-09~1.20>make
MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp.
Error makefile 5: Command syntax error
Error makefile 13: Command syntax error
Error makefile 15: Command syntax error
Error makefile 17: Command syntax error
*** 4 errors during make ***

Also if I load the source into Borland C then there are error
messages:

"Error TCC.C 21: Unable to open include file 'CONFIG.H'"

There is not CONFIG.H in the compressed file I downloaded.

Can anyone help me on how to get an implementation source for the Tiny
C Compiler for Windows 32?

Thanks a lot
regards
Werner Nussbaumer

[Mark A. Odell]

w.**********@datacomm.ch (Werner Nussbaumer) wrote in
news:60**************************@posting.google.c om:

I am searching for a version of the Tiny C compiler for Windows 32. I
downloaded a version from http://fabrice.bellard.free.fr/tcc/ but the
make command displayed error messages:

I think google would be a better bet than here to ask such a question.
Your question is not about the C language but about a particular compiler.
Thus off-topic. Sorry.

--
- Mark ->
--

[Christopher Benson-Manica]

Werner Nussbaumer <w.**********@datacomm.ch> spoke thus:

I am searching for a version of the Tiny C compiler for Windows 32. I
downloaded a version from http://fabrice.bellard.free.fr/tcc/ but the
make command displayed error messages:
Your post is off-topic for comp.lang.c. Please visit

http://www.ungerhu.com/jxh/clc.welcome.txt
http://www.eskimo.com/~scs/C-faq/top.html
http://benpfaff.org/writings/clc/off-topic.html

for posting guidelines and frequently asked questions. Thank you.

(But I'll continue...)
P:\DEVELOP\c2\TCC-09~1.20>make
MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp.
Error makefile 5: Command syntax error
Error makefile 13: Command syntax error
Error makefile 15: Command syntax error
Error makefile 17: Command syntax error
*** 4 errors during make ***
$10 says that the makefile uses GNU make syntax, which is not
compatible with the syntax expected by Borland make. You can either
hack the makefile yourself (borland.public.cppbuilder.commandlinetools
on the news server newsgroups.borland.com can help) or get a win32
executable for GNU make (google).
Also if I load the source into Borland C then there are error
messages: "Error TCC.C 21: Unable to open include file 'CONFIG.H'" There is not CONFIG.H in the compressed file I downloaded.
Whatever config.h is, it isn't standard, so it's no wonder that
your Borland implementation doesn't have it. Ask the maintainer of
the compressed package if you can, or google for it.
Can anyone help me on how to get an implementation source for the Tiny
C Compiler for Windows 32?

Well, you've got some of it, apparently. You might also try using the
latest free Borland suite (with the 5.5.1 compiler) if you aren't
already.

--
Christopher Benson-Manica | I *should* know what I'm talking about - if I
ataru(at)cyberspace.org | don't, I need to know. Flames welcome.

[Dan Pop]

In <cd**********@chessie.cirr.com> Christopher Benson-Manica <at***@nospam.cyberspace.org> writes:

Werner Nussbaumer <w.**********@datacomm.ch> spoke thus:

Also if I load the source into Borland C then there are error
messages:

"Error TCC.C 21: Unable to open include file 'CONFIG.H'"

There is not CONFIG.H in the compressed file I downloaded.

Whatever config.h is, it isn't standard, so it's no wonder that
your Borland implementation doesn't have it. Ask the maintainer of
the compressed package if you can, or google for it.

When you don't have the slightest clue about the issue, it's much better
to keep your mouth shut. No point in misleading the OP.

It is extremely common in the open source world for applications to have
a config.h header file, that is either automatically generated by the
application building procedure (the most common case these days) or
produced by the user building the application, by editing a template
file provided by the developer. This file contains information that is
specific to the local system and the local installation of the application
being built. There is absolutely no point in trying to get it from
anywhere else. Carefully read the application building instructions and
follow them ad litteram, instead of compiling anything by hand.

And if you don't understand what the documentation is asking you to do,
ask a more experimented person to do the job instead.

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[Christopher Benson-Manica]

Dan Pop <Da*****@cern.ch> spoke thus:

And if you don't understand what the documentation is asking you to do,
ask a more experimented person to do the job instead.

I suppose I should have told OP to read the documentation. I don't
believe I said anything false, however.

--
Christopher Benson-Manica | I *should* know what I'm talking about - if I
ataru(at)cyberspace.org | don't, I need to know. Flames welcome.

[Dan Pop]

In <cd**********@chessie.cirr.com> Christopher Benson-Manica <at***@nospam.cyberspace.org> writes:

Dan Pop <Da*****@cern.ch> spoke thus:

And if you don't understand what the documentation is asking you to do,
ask a more experimented person to do the job instead.

I suppose I should have told OP to read the documentation. I don't
believe I said anything false, however.

Sending the OP to google for config.h was idiotic in the extreme.

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[Gregory Pietsch]

w.**********@datacomm.ch (Werner Nussbaumer) wrote in message news:<60**************************@posting.google. com>...

Hello

I am searching for a version of the Tiny C compiler for Windows 32. I
downloaded a version from http://fabrice.bellard.free.fr/tcc/ but the
make command displayed error messages:

P:\DEVELOP\c2\TCC-09~1.20>make
MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp.
Error makefile 5: Command syntax error
Error makefile 13: Command syntax error
Error makefile 15: Command syntax error
Error makefile 17: Command syntax error
*** 4 errors during make ***

Also if I load the source into Borland C then there are error
messages:

"Error TCC.C 21: Unable to open include file 'CONFIG.H'"

There is not CONFIG.H in the compressed file I downloaded.

Can anyone help me on how to get an implementation source for the Tiny
C Compiler for Windows 32?

Thanks a lot
regards
Werner Nussbaumer

<guess>

For Unix/Linux-style packages, the <config.h> file is generated by a
"configure" script in the package, which also generates a Makefile
from Makefile.in .

You might want to look at the config.h.in file, copy it to config.h,
and manually tweak the symbols within until everything looks okay.

</guess>

Gregory Pietsch

[Werner Nussbaumer]

GK**@flash.net (Gregory Pietsch) wrote in message news:<3a**************************@posting.google. com>...

w.**********@datacomm.ch (Werner Nussbaumer) wrote in message news:<60**************************@posting.google. com>...

Hello

I am searching for a version of the Tiny C compiler for Windows 32. I
downloaded a version from http://fabrice.bellard.free.fr/tcc/ but the
make command displayed error messages:

P:\DEVELOP\c2\TCC-09~1.20>make
MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp.
Error makefile 5: Command syntax error
Error makefile 13: Command syntax error
Error makefile 15: Command syntax error
Error makefile 17: Command syntax error
*** 4 errors during make ***

Also if I load the source into Borland C then there are error
messages:

"Error TCC.C 21: Unable to open include file 'CONFIG.H'"

There is not CONFIG.H in the compressed file I downloaded.

Can anyone help me on how to get an implementation source for the Tiny
C Compiler for Windows 32?

Thanks a lot
regards
Werner Nussbaumer

<guess>

For Unix/Linux-style packages, the <config.h> file is generated by a
"configure" script in the package, which also generates a Makefile
from Makefile.in .

You might want to look at the config.h.in file, copy it to config.h,
and manually tweak the symbols within until everything looks okay.

</guess>

Gregory Pietsch

Thank you, your guess was correct.

Regards
Werner Nussbaumer