RE: Fwd: [Bug c++/14563] octave built under Cygwin very slow]

[Paul Billings]

I had no trouble building octave 2.1.71 with gcc3.4.4.  Unfortunately, it
does not bring up a command prompt (or any of the initial text output) --
just hangs with CPU usage 0% and ctrl-c doesn't work.  I haven't traced
through to see what it's waiting for.  Since my real desire is octave speed
and from other negative comments I've seen about that version, I don't think
I will pursue the gcc3.4.4 route.

I started to build gcc3.3.3 with --disable-sjlj-exceptions, but having never
done it before, I was a bit overwhelmed by what seemed to be required.

Paul


> -----Original Message-----
> From: Andy Adler [mailto:address@hidden
> Sent: Saturday, August 06, 2005 2:31 AM
> I have two comments:
>   - I'm also seeing the compile problems with gcc3.4; however Paul
>     Soderlind sent me a note that he had no problem with gcc3.4.
>     Would anyone else like to comment on their experiences with
>     octave/cygwin/gcc3.4?
>
>   - Has anyone tried to compile octave with a gcc version compiled
>     with --disable-sjlj-exceptions?
>
> --
> Andy Adler