Hi!
Sorry for rising the matter. I suppose that Charles is right.
At 23:27 30/09/2014, Charles Gordon wrote:
Porting old code to a modern compiler or OS is not for the faint of heart.
Yes. I thought my old code was robust enough (it
cam from QNX and I ported it under DOS/Window
using Borland years ago and it ran without problem for decades).
If your C is rusty, as it shows given your
questions, you are going down a rough roadÂ…
If you cannot compile with gcc, first fix
that. You probably defined some string
functions that conflict with those of the
glibc. Try using some of the gcc flags that
prevent builtins or enforce strict standard conformance.
So, it seems I have to rewrite it and test it
step by step. If I read you correctly (I am not a
developper, just a user developping my own
operational tools as a powefull enough function
library) my best bet is to rewrite for it. I
suppose I will enjoy adding a few things.
From what you say, I should go for gcc
compatibility under windows to be sure it
compiles with TCC and probably everywhere.
You can also hide the glibc functions by
defining macros before the #include lines and undefine them afterwards.
Yeap. But I think I will try to offer me a
refurbished library as a Xmas C gift :-)
btw, would you know a clean and clear uptodate C
documentation including internetworking tools?
Thx to every one
jfc
_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
