"Thomas Preud'homme" wrote
> libtcc1.a isn't built on arm architecture but tcc_add_runtime add
libtcc1.a
> unconditionally. I used a macro to not load libtcc1.a on arm but a
replacement
> of tcc_add_file by something like :
libtcc1.a wasn't being built on Linux either, so my mob branch patches
The LIBS=. line was left over from experimental work on
--disable-static, sorry. It has been removed. I think everything is back
to normal. I tried to make all the changes atomic, but it looks like
that one got out of the box.
___
Tinycc-devel mailing
I thought you might find this interesting. I've made a pseudocode
compiler and learning aid that integrates with TCC, but doesn't depend
on it.
If I can get TCC into Fedora, I plan to eventually use the new dynamic
library, libtcc.so at runtime instead of wrapping "tcc -run" with a
script like it
I was a really bad coder. Sorry. I get it working first, then go back
and find out how to do it standardly. I think this last push fixed up
most of the major problems in my branch. This brings things in line with
the Fedora rpm I'm building.
http://thenerdshow.com/rpm/tinycc-git20100114-2.fc13.src.
I fixed my selinux patch, so it's better integrated into the way tcc
does things. It was really quite terrible. Now it works with programs
that use libtcc, if ever there be ones...
I also pushed a script to build a win32 version of libtcc1.a for
cross-compiling on x86 and x86_64 arch.
And another
I recently committed a patch to the mob branch for Selinux compatibility
using information obtained from
http://people.redhat.com/drepper/selinux-mem.html
Selinux is a security package that is installed by default on Fedora.
TCC -run segfaults on Fedora because Selinux prevents writing and
executi
