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 reference to get started other than on the website? I don't want to ask questions that may have been answered elsewhere. thanks, and i greatly appreciate any/all help getting started. stephen On Tue, Dec 9, 2014 at 2:03 PM, stephen Turner <stephen.n.tur...@gmail.com> wrote: > 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 expression syntax > [[] > > Is there any log files generated i can provide? i did not see the usual > config.log that gcc would output. > > thanks, > stephen > > On Tue, Dec 9, 2014 at 10:31 AM, stephen Turner < > stephen.n.tur...@gmail.com> wrote: > >> 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 >>> <stephen.n.tur...@gmail.com> wrote: >>> > I have found tcc and wondered how viable it is as a alternative to gcc >>> and >>> > clang/llvm for my uses >>> >>> I'm actively using tcc as my main compiler, only switching back to GCC >>> on demand for eg. running tests with valgrind (as tcc's debug symbols >>> currently do not work with valgrind). >>> So far, it works perfectly for my C projects, producing reasonably >>> small output binaries very fast. >>> You should of course be aware that tcc does almost no optimizations, >>> instead translating the code almost literally - which I perceive as an >>> advantage (The reasoning being that when my code is performing well >>> when compiled without lots of optimization, it will most likely run >>> even better with an optimizing compiler). >>> >>> > Does it use makefiles? >>> If you want to use them. Makefiles are processed by make, not by tcc, >>> so that's completely independent. In most shells, you can try to run >>> make with tcc instead of whatever your default C Compiler is by >>> running >>> user@box:/path/to/project$ CC=tcc make >>> This might not work if the project you're trying to compile is using >>> functionality that tcc does not support. >>> >>> Hope that helps! >>> >>> Regards, >>> cbdev >>> >>> _______________________________________________ >>> Tinycc-devel mailing list >>> Tinycc-devel@nongnu.org >>> https://lists.nongnu.org/mailman/listinfo/tinycc-devel >>> >> >> >
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
