Hello, now that the gcc 3.2 transition is over, does this bug still apply ? Cheers, -- Bill. <ballombe@debian.org>