The problem with the VAX case is that a cross build means the tools 
directory is build native for the host, so you will not ever see this 
problem (the one I'm talking about). So cross-builds for the VAX will 
run fine, even though a native build will not.

But anyway, it's a whole different (and easier delt with) problem when 
some code complains than when all you get is a core dump.

	Johnny

Matt Dainty wrote:
> On Tue, 2005-12-13 at 01:24 +0100, Johnny Billquist wrote:
> 
>>The specific problem you hit upon is that when the tools build comes to 
>>groff, it will fail late in the build, when creating some document, 
>>because grn segfaults.
> 
> 
> Funnily enough I've seen a similar problem with a friend of mine
> cross-building for sparc on a Fedora Core 4 Linux box.
> 
> 
>>If I were to guess that is because some code generated by gcc is wrong 
>>when using -O2. Nobody ever seems to try to find the problem, but it has 
>>been verified that using -O0 in those few cases where it happens will work.
>>I found it while building one file in kermit as well.
>>It's rare, but it do happen occasionally.
> 
> 
> This particular problem seems to get caught by the version of glibc on
> Fedora which has some malloc() checking. It detects a "double free or
> corruption" and aborts. Disabling/ignoring the checks allows the build
> to continue in this case.
> 
> IIRC this was building on the netbsd-2 branch.
> 
> Matt

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol