Le dimanche 10 juillet 2011 18:05:57, grischka a écrit : > Thomas Preud'homme wrote: > > I wrote the code yesterday. Please take a look. Still missing is the > > handling of elf_interp but this must be added anyway without this > > option. > > Well, to me the better patches are those that make the code smaller > rather than bigger ;) Ok. > > As I understand it is possible to support multilib without any special > code in tcc. Without CONFIG_TCC_MULTILIB_SUBDIR, AFF_MULTILIB, > CONFIG_TCC_EXTRA_LDDIR, CONFIG_TCC_INCSUBDIR, just without anything > "MULTI_EXTRA_SUB" whatsoever. > > Do you think that is possible? Yes, I think so if the include and library path can be colon seperated. I understand your concern about tcc to stay tiny. Without touching tcc itself, would it be ok to add a --multilib-subdir switch in configure which would set the library and include path correctly? That way the compiler itself would stay small but give a convenient interface at build time. > > > By the way, is this normal that only X86_64 ld.so uses CONFIG_TCC_LDDIR > > or does the other ld.so also lack the use of this macro? > > Likely lack: > $ git checkout release_0_9_25 tccelf.c > > /* name of ELF interpreter */ > #if defined __FreeBSD__ > static char elf_interp[] = "/usr/libexec/ld-elf.so.1"; > #elif defined TCC_ARM_EABI > static char elf_interp[] = "/lib/ld-linux.so.3"; > #elif defined(TCC_TARGET_X86_64) > static char elf_interp[] = "/lib/ld-linux-x86-64.so.2"; > #elif defined(TCC_UCLIBC) > static char elf_interp[] = "/lib/ld-uClibc.so.0"; > #else > static char elf_interp[] = "/lib/ld-linux.so.2"; > #endif > > --- grischka
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
