🚀 go-pugleaf

	Posts like this are ones that I HAVE to reply to...

In article <4gvhqc$lqs@news.ccit.arizona.edu>, Dean Schulze wrote:
>    Ian T. Zimmerman writes:
>
>>I am really, really fed up. I moved to ELF something like 2 months ago
>>and since then it seems I haven't done anything else but downloading
>>and upgrading. 
>
>    I've just about reached my limit with gcc/Linux too.  Linux seems
>wonderful, but gcc for Linux is the worst compiler I have ever used.
>Version 2.7.0 crashed with an internal error and signal 11 (SIGSEGV)
>when I tried to compile its own source code during g77 installation!
>I installed the binaries for v2.7.2, but when I built the binaries for
>a C++ numerical library (newmat08) the example program crashes.  When
>I set a breakpoint in the DDD debugger at the point in the code where it
>crashes I get an internal error in DDD when the program runs to that
>point.  The version of xxgdb that came with my Linux distribution suffers
>from character doubling.  If I use any optimization at all when compiling
>newmat08 gcc crashes with an internal compiler error.

	First of all, are you sure that it's GCC's fault?  You could
have some serious memory corruption if GCC segfaults at random places
all the time.  Please read the Linux FAQ; it's there for you to RTFM.
In particular, look at the Sig11 FAQ which the Linux FAQ mentions
(I forgot where it is).  As for xxgdb's double-character output, please
upgrade xxgdb to 1.12, found at ftp.x.org's contrib program archive.

>    I've been trying to get Linux (Slackware 3.0) to the point where I
>can get some work done for a month now, and I just keep uncovering more
>bugs.  (And I haven't even gotten to the point where I start using
>g77.)  Most of the problems are with gcc.  If gcc were a commercial
>product FSF would go out of business very quickly.  gcc makes
>Microsoft's compilers look good.

<FLAME MODE ON>

	Excuse me?  Are you trying to bash GCC just because of a single
bad experience?  On my system, I had no problems with GCC 2.7.0 and
libc 5.0.9 up to now.  Please make sure your setup and/or your hardware
isn't broken.  In particluar, Slackware 3.0 is known to have various
configuration/package version bugs; no software is immune to problems.
But DON'T put down the FSF for their volunteer efforts, unless you would
like to help them fix whatever problem you might happen to have with GCC.

>    I'm ready to go back to Windows NT and try Watcom's compilers.
>(I switched to Linux after trying Microsoft's compilers for mixed
>language programming.  They simply don't work.)  The other alternative
>is to use my 120 MHz pentium as a terminal and telnet to a real UNIX
>machine for my work.
>
>    Linux isn't fit for any real work at this point in time due to
>the lack of a decent compiler.

	Maybe you just need to stop an think about what it is that's
not working?

<FLAME MODE OFF>

>Dean Schulze


..........----------==========**********==========----------..........
                        Arthur Dikran Jerijian
         UCLA Undergraduate, Computer Science and Engineering
            E-mail until June 1997: jerijian@seas.ucla.edu
          World Wide Web: http://www.seas.ucla.edu/~jerijian
..........----------==========**********==========----------..........