I couldn't figure out how to correctly use -Dstrtold=strtod, so I did a
simple find/replace to test build. It worked, but I would like to do this
correctly.
I did a search on -D, Makefiles, -D gcc options and grepped for D within
the source directory. I couldn't find/see anything that resembled t
On Wed, Sep 11, 2013 at 11:48 PM, Cayce Pollard wrote:
> Just saw your email as I was getting ready to post my next questions.
> 1) should I just find/replace in the code or make an alias to strtod?
>
i _suspect_ that -Dstrtold=strtod might do the trick for you.
--
- stephan beal
http://wan
I suspect you're right...now off to find out where that particular option
goes...
(still grepping my way through pages of gcc documentation and Android
internals)
Will the same work for __clear_cache? I suspect not, based on a cursory
examination of that and cacheflush, but I'd be happy if someon
On Wed, Sep 11, 2013 at 03:40:15PM -0500, Cayce Pollard wrote:
> ./../tinycc/tccpp.c:1961: error: undefined reference to 'strtold'
Just substitute strtod for strtold.
It has probably been omitted from Android's libc because
long double == double on ARM nowadays (i.e. with EABI or VFP).
Daniel
Just saw your email as I was getting ready to post my next questions.
1) should I just find/replace in the code or make an alias to strtod?
2) Android's version of __clear_cache is cacheflush, can I make an alias
for that as well?
I
On Wed, Sep 11, 2013 at 4:38 PM, Daniel Glöckner wrote:
> On
Ignore my previous message...bionic libc doesn't have strtold.
Back to the drawing board...
On Wed, Sep 11, 2013 at 3:40 PM, Cayce Pollard wrote:
> Hello,
> When building tinycc using the Android NDK standalone toolchain, I get the
> following error:
>
> Putting child 0x01bcc300 (tcc.o) PID 2437
Hello,
When building tinycc using the Android NDK standalone toolchain, I get the
following error:
Putting child 0x01bcc300 (tcc.o) PID 24373 on the chain.
Live child 0x01bcc300 (tcc.o) PID 24373
In file included from ./../tinycc/tcc.c:24:0:
./../tinycc/tcc.h:943:20: error: conflicting types for '
Hi. Just a note of thanks to Ramsey for the patch and to Thomas for
pushing it. I appreciate the responsiveness.
Arnold
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Gabriel Corneanu wrote:
Sorry, replied to private instead of list:
I have just checked and mingw generates "foo@4" where tcc generates
"_foo@4"; so it seems that it doesn't work quite the same.
It is a bug in mingw.
It would work the same if it respects the "leading-underscore" flag.
How,
Sorry, replied to private instead of list:
I have just checked and mingw generates "foo@4" where tcc generates "_foo@4";
so it seems that it doesn't work quite the same.
It would work the same if it respects the "leading-underscore" flag.
Anyway, I still don't quite get the reasons; all Windows (
Gabriel Corneanu wrote:
Hello again,
First thanks to grischka for previous quick fix.
Now I have another small issue; using "stdcall" always generate some
name mangling for function names, in libtcc.c line ~499.
It ignores the "leading_underscore" option, which is otherwise respected
a few lin
Hello again,
First thanks to grischka for previous quick fix.
Now I have another small issue; using "stdcall" always generate some name
mangling for function names, in libtcc.c line ~499.
It ignores the "leading_underscore" option, which is otherwise respected a
few lines below (512).
The effect i
Le mercredi 11 septembre 2013 09:09:28 Harshvardhan a écrit :
> Hello. I faced several problems compiling tcc-0.9.26 for FreeBSD x86-64,
> First of all it didn't detected that I am using x86-64 CPU and that
> FreeBSD don't use ldl. I manually edited Configuration script to change
> 'unknown' cpu to
13 matches
Mail list logo
