Thomas Preud'homme wrote:
So if the file system layout change it's quite normal that gcc have to handle
these changes.
Why is that normal, quite? We just proved that tcc can work for
multiarch without any encoded knowledge at all what multiarch is.
./configure --prefix=/home/robotux/local --
sysincludepaths="/usr/local/include/i386-linux-
gnu:/usr/local/include:/usr/include/i386-linux-gnu:/usr/include:
\\\\\\\\b/include/i386-linux-gnu:\\\\\\\\b/include" --libpaths=/usr/lib/i386-
linux-gnu:/usr/lib:/lib/i386-linux-gnu:/lib:"/usr/local/lib/i386-linux-
gnu:/usr/local/lib" --crtprefix="/usr/lib/i386-linux-gnu:/usr/lib"
Oops! If this is \\\\\\\\b/include with 8 backslashes, then
I think we must use something else.
What about ?B as in "?B/include"? Or maybe "{B}/include"?
After that (and of course installing the 32 bits libraries), everything worked
as expected. I could compile a simple test.c file and execute it.
Thanks for testing,
--- grischka
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
