On Tue, 25 Jun 2002, WE HATE SPAM wrote: > Has anyone built 1.4 on Redhat 7.1 (gcc 2.96) attempting to compile > lsh 1.4 causes the compiler to die with Internal compiler error in > add_abstract_origin_attribute, at dwarf2out.c:9296 (I found it > listed as a known bug at: > > http://gcc.gnu.org/ml/gcc-bugs/2001-12/msg00804.html )
Red Hat 7.1 shipped with gcc-2.96-81, but on 2001-06-22, Red Hat released gcc-2.96-85 as an errata update. If you're getting crashes, make sure that you've updated to gcc-2.96-85. If you're using gcc-2.96-85, and you're still getting crashes, file a Bugzilla report with Red Hat. On Tue, 25 Jun 2002, [EMAIL PROTECTED] wrote: > Use gcc3 instead, it works fine and, I believe, is shipped with > redhat 7. No. All Red Hat 7.x releases have shipped with gcc-2.96. Red Hat 7.2 also shipped with gcc-3.0.1, but Red Hat 7.2 was the only Red Hat release to ship with gcc version 3 (even as an alternate, let alone the primary compiler). On Tue, 25 Jun 2002, Niels M�ller wrote: > Don't use gcc-2.96. Either downgrade to 2.95, or upgrade to gcc-3. The use of gcc-2.96 is preferable to either 2.95 or 3.0.x. 3.1 is probably preferable to 2.96 at this point, but since Red Hat doesn't yet ship with gcc-3.1, Red Hat users either have to go grab the Rawhide RPMs, or else build gcc-3.1 themselves. Gcc-2.96 gets bashed a lot, but most of the bashing is undeserved: http://bero.org/gcc296.html On Tue, 25 Jun 2002, WE HATE SPAM wrote: > Finally, a suggestion. liboop should be added as a pre-requisite on > the web site (zlib and gmp are listed, liboop is not). Speaking of liboop, when I built it as an RPM, I sent a copy of my spec file back to the author. I never heard back from him. If there's interest, I can make the RPMs, source RPMS, and/or spec file available... -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA
