Ok grischka, thanks for noticing, but you seem to refer to cross-compiling _with_ tinycc. While i'm too cross-compiling tinycc _itself_, with gcc and tcc (several variants). Furthermore it's hundreds of ebuilds wrapped into crossbuild setup with tcc, some of which misbehaved because cross-compilation support often isn't sufficiently maintained and tested. Hence mentioned two environment variables were helpful, because the tcc configure/make-cross does not and cannot address all these issues.
Furthermore the --triplet configuration seems to be flawed with crt search path,
config-extra.mak seems to override this, which is ok,no need to change anything.
And config-extra.mak is a compile-time configuration of tinycc, while the
proposed TCC_ environment variables could be set anytime later however desired,
runtime without clashes.
I merely posted the helper patches in case anyone else ever seeked to use
tinycc as a complete system-toolchain, which noone did before i guess.
I have to depart again from tinycc for other tasks for a while,
stabilizing a few driver-backports to linux-2.4 for usb-ethernet, it's working
already but occasionally hits instability with linux-tcc kernel. Then SATA/IDE
isn't detected always, and i do want to make sure the tinycc-driven system does
boot and work with sufficient hardware support always on x86_32, bare-metal and
inside virtual machines, so other developers can join, seeing tinycc-toolchain
driving a complete operating system. From tinycc-devel side all seems in check,
for x86_32, but there's other tasks remaining unrelated to tinycc-devel.
On 2026-01-02 20:11, grischka via Tinycc-devel wrote:
> On 02.01.2026 00:18, Michael Ackermann via Tinycc-devel wrote:
> > - to prevent further issues two optional environment variables got
> > introduced
> > TCC_LIBRARY_PATH and TCC_CPATH to force overriding ALL search paths
> > without ...
>
> Well, the supported way to build an 'i386-tcc' cross-compiler is:
>
> ./configure
> make cross-i386
> make install
>
> which is supposed to work with standard gnu cross-devel files.
>
> In case when it does not, paths may be specified explicitly in a
> 'config-extra.mak' (that you'd create), as in (for example):
>
> CRT-i386 = /usr/i686-linux-gnu/lib
> LIB-i386 = {B}:/usr/i686-linux-gnu/lib
> INC-i386 = {B}/include:/usr/i686-linux-gnu/include
>
> See also 'make help'
>
> -- gr
>
>
> _______________________________________________
> Tinycc-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
--
Michael Ackermann
Mail mailto:[email protected]
signature.asc
Description: Digital signature
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
