Le mardi 9 décembre 2014, 14:03:10 stephen Turner a écrit :
I compiled musl-libc with gcc as well as tcc. Tcc appears to be in good
working order but when i use tcc to compile musl-libc it errors out.
The command im using is CC=/path/to/tcc ./configure --prefix=/dest/folder
Thanks, that is helpful.
I read mention of TCC including the linker, does this mean binutils is not
necessary?
I would be very interested to see C++ be included.
On Tue, Dec 9, 2014 at 9:54 AM, cbdev c...@cbcdn.com wrote:
Hi Stephen,
On Tue, Dec 9, 2014 at 7:19 AM, stephen Turner
I compiled musl-libc with gcc as well as tcc. Tcc appears to be in good
working order but when i use tcc to compile musl-libc it errors out.
The command im using is CC=/path/to/tcc ./configure --prefix=/dest/folder
--target=i386-linux-musl
the error i receive is crt/i386/Scrt1.s:17: error: bad
perhaps im not using this correctly. I built a quick chroot env with a
static tcc and musl-libc. performing ./configure it still believes gcc is
being used when TCC is available in the /bin dir and appears to be compiled
correctly. (it responds when called anyways)
Is there documentation i can
Sorry, it was unexpected that there would be a config flag to set the
compiler.
Im getting what appears to be code related compile errors now. How can I
collect data that would help troubleshoot such issues? I successfully
compiled the gnu make application in the chroot env. I tried running
I have found tcc and wondered how viable it is as a alternative to gcc and
clang/llvm for my uses. I checked the website but it appears to have been
dead for several years.
Does it use makefiles?
can it be a simple drop in replacement for GCC (atleast for c if not c++
too)
i have done a few
