[Brian Foddy <brian.foddy@xxxxxxx>]

No, I didn't have any m64.  I was using gcc 2.95.3 which doesn't
support 64bit code.

The only options I had specified were
CFLAGS="-O2 -mcpu=ultrasparc"

It was probably the ultrasparc option.  Thinking back, I know this
version of gcc has a infrequent coredump when optimizing for
ultrasparc (its an official bug resolved last summer I think).  
There was no coredump, but it could have generated
bad code anyway.  When I unset CFLAGS and configed and compile
it worked fine.  I don't have any more insight than that.

Thanks,
Brian

Guy Harris wrote:

> On Wed, Nov 06, 2002 at 04:26:03PM -0600, Brian Foddy wrote:
>  
>
> > Update:  I took out all the compile flag optimizations, reconfig and 
> > compile and
> > no more core dump.  I had -mcpu=ultrasparc as the main optimization.
> >    
>
> You didn't also use "-m64", presumably.  (Don't do that unless you know
> that *all* the libraries with which you're building Ethereal include
> 64-bit versions.)
>
> What other optimizations did you use, if any?  Some of them might either
> generate buggy code or code that is, for whatever reason, not binary
> compatible with the code in one of the libraries (e.g., GTK+).
>
>
>