tcc builds ELF executable in the way not understood by FreeBSD. There is no quick fix for that, afaik. ELF executable linkage part of tcc must be adopted for building native FreeBSD exe-s. However, building Linux executables and linking them against /usr/compat/linux libraries might work. I spent some time before, trying to make 'native linkage' work on FreeBSD, but not finished the work yet. It is half-way complete. Simple programs do execute, more complex ones coredump.
On 7/23/05, Brett Henley <[EMAIL PROTECTED]> wrote: > Hi everyone, > > I"m running FreeBSD 5.4-p1 with GCC 3.4.2 > I built tcc 0.9.23 and it is great using -run, I have > wanted something like cint and this goes there and is > even better. So hurrah and thank you everyone who > has worked on this. > > There is a problem however that I've been unable > to resolve on my own. If I compile a program even > simple like hello.c and try to run the -o or a.out file > I get a segfault and the core dumps. I have attempted > to use gdb but the symbols leave me lost. > > I have noticed that building tcc-0.9.23 on linux, > -o and a.out files work just dandy. > > Wherein using tcc to perform as a script engine is > terrific. I wanted to build other programs with tcc > as the compiler. But when configure tries to test > the compiler the executable fails and life sucks. ;) > > Any suggestions would be appreciated. > > > > > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/tinycc-devel > _______________________________________________ Tinycc-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/tinycc-devel
