Ingo Weinhold schrieb:
On 2009-03-03 at 10:44:24 [+0100], Artur Wyszynski <aljen-mlists@xxxxxxx> wrote:Stephan Aßmus pisze:[...] I was still getting the vsprintf() crashes, but I made the image with "jam update-all" (cleaned out the develop/headers folder before).Could you write steps how to reproduce this ? It seems to run fine here ;/Anyways, the incompatibility with certain C programs is quite inconvenient. GCC for example doesn't run for me. Is that supposed to work, or may that be another side-effect of jam update-all?Yep, all current gcc4 stuff built with gcc4 for old libroot need to be rebuilt, including gcc4 itself from OptionalPackagesI'm wondering, does anyone see problems with switching to a new libroot while still shipping a compatibility libroot? After all the only reason for using the current glibc mishmash is for binary compatibility with BeOS.
If the new one doesn't introduce problems which weren't there before, I'd be fine with it.
Best regards, -Stephan