gcc 3.2.1 and bison 1.50

Matthias, Have you tried using the new bison 1.75 release from ftp.gnu.org? Perhaps you might have better luck with the gcc 3.2.1 builds using that one. Jack

Re: gcc 3.2.1 in sid?

On Thu, Oct 17, 2002 at 11:50:06PM +0200, Matthias Klose wrote: > Jack Howarth writes: > >Now that glibc 2.3.1 is in sid, what are the plans > > for the transition to gcc 3.2.1? > > we are waiting for an transition plan. My assumption was Jeff would > propose a transition plan for a _coordinat

Re: gcc 3.2.1 in sid?

Jack Howarth writes: >Now that glibc 2.3.1 is in sid, what are the plans > for the transition to gcc 3.2.1? we are waiting for an transition plan. My assumption was Jeff would propose a transition plan for a _coordinated_ transition of glibc and gcc. It seems a bit late for that :-( > I am as

gcc 3.2.1 in sid?

Now that glibc 2.3.1 is in sid, what are the plans for the transition to gcc 3.2.1? I am assuming we are waiting for the official gcc 3.2.1 release. That should be soon however. Are we still planning a bulk rebuild of each arch? I believe ppc should be in excellent shape for the transition. The

Bug#165180: gij-3.0 does not depend on libgcc1 (libgcc_s.so.1) which is required for its operation.

Package: gij-3.0 Version: 1:3.0.4-13 dh_testdir /usr/bin/make make[1]: Entering directory `/tmp/buildd/ttthreeparser-1.4' Translating TTCN3Lexer.g /usr/bin/gij-3.0: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory make[1]: *** [TTCN3L

gcc-2.95 bugs on m68k: what to do ?

I have several packages (e2fsprogs, bigloo) that fail to build on m68k, apparently due to one or more gcc bug(s). Maybe that's the same as #146006, and #89023, but I can't tell that myself. Madkiss suggested forcing the use of gcc-3.2. But if this compiler is officially broken on m68k, I'd rathe