Rob Landley wrote:
The reason you can't run a glibc version of gcc against uClibc is that pieces of gcc like libgcc_s.so link against their libc, and leak references to that libc. So if you ever divide by a 64 bit number on a 32 bit platform or weird corner cases like that, a reference to glibc sneaks into your uClibc program. Since libgcc is part of the gcc source code, the only way to build a version of that library which leaks a reference the _right_ libc is to rebuild gcc against uClibc, from source code.
This is just because libgcc is dynamically linked. You can change that, only producing a static version, which in turn never introduces references to a specific libc. Don't ask me how to do that officially, because my setup uses completely different makefiles alltogether. cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tinycc-devel
