> I didn't look much at the patch but noticed it hardcodes i686 as the target. > Is your system a 32 bit intel system? If no, that might explain what is the > problem you encounter.
No, sadly I'm on a 64-bit host. > Also you can try playing with the number of / (adding or removing one) > in line 396 of the patch (the one that sets CONFIG_TCC_CRTPREFIX. Noted, thanks. > > At this point I'm taking a step back and asking if there > > are any existing recipes for building a static compiler > > that can be used in a static-only environment (with no ldd > > or linker present). > > I suppose you mean no ld.so. Yes, that is correct. > Currently tcc fails to work with -static with glibc but I don't know > if that is the case with uclibc. I know there is some line about > uclibc in tcc's code so it should be supported but I never tried. I've tried to make it work, but not yet hit success. The issue mostly resolves around it generating static code - actually compiling tcc itself seems simple enough. Steve -- _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
