priority change on your package(s)

In fixing bug #301138, several packages have been lowered to optional priority from standard priority, reflecting that our "standard" user is not a developer, and should not have a development environment installed. If you're on the cc list, your package(s) have been affected. Here's the compl

Bug#391268: _REENTRANT defined when compiling non-threaded code

Package: libstdc++6 Version: 4.1.1-15 Severity: important This is already reported upstream: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11953 It was fixed, but only on the redhat 4.1 branch. The fix is needed on trunk, and the general 4.1 branch. A simple testcase: test.cpp: #include #ifdef _

Bug#329715: gcc-4.0_4.0.1-9(powerpc/unstable): fails to build without deprecated BSD ptys

Package: gcc-4.0 Version: 4.0.1-9 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-4.0_4.0.1-9 on voltaire by sbuild/powerpc 65 > Build started at 20050922-1710 [...] > ** Using build dependencies supplied by package: > Build-Depends: dpkg-de

Bug#256041: libmudflap ...

Looking at the build log, it only looks like the "libmudflap" dir is affected, at least up until the point where the build failed on both mips and mipsel.

Bug#256041: gcc-snapshot_20040620-1(mipsel/unstable): configure built with out-of-date libtool.m4

Package: gcc-snapshot Version: 20040620-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-snapshot_20040620-1 on repeat.rfc822.org by > sbuild/mipsel 1.170.5 > Build started at 20040621-0833 [...] > ** Using build dependencies supplied by p

Bug#224875: dchub_0.4.5-3(mips/unstable): mips{,el} spec file specifies -lthread, not -lpthread

Package: gcc-3.3 Version: 0.4.5-3 Severity: serious There was an error while trying to autobuild your package: > Automatic build of dchub_0.4.5-3 on resume.rfc822.org by sbuild/mips 1.170.4 > Build started at 20031214-0442 [...] > ** Using build dependencies supplied by package: > Build-Depends

Bug#203835: patch

tag 203835 + patch thanks There is a patch for 3.3 that looks to have been ignored on the mailing list at: http://gcc.gnu.org/ml/gcc-patches/2003-08/msg01356.html

dsc still lists these as being built

The dsc file still lists the packages as being built, because they are in the control file when the source is built. I'm removing them, but please update cvs (if there is another upload) so that they aren't listed.

Bug#196915: gcc-3.3_1:3.3ds9-3(powerpc/unstable): FTBFS: treelang still fails

Package: gcc-3.3 Version: 1:3.3ds9-3 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.3_1:3.3ds9-3 on voltaire by sbuild/powerpc 1.170.2 > Build started at 20030604-0432 [...] > ** Using build dependencies supplied by package: > Build-Depen

Bug#195899: gcc-snapshot_20030531-2(mips/unstable): FTBFS: use -O2 for mipsen?

On Tue, Jun 03, 2003 at 11:52:59AM +0200, Matthias Klose wrote: > Ryan Murray writes: > > Package: gcc-snapshot > > Version: 20030531-2 > > Severity: serious > > > > There was an error while trying to autobuild your package: > > > > It looks like

Bug#195899: gcc-snapshot_20030531-2(mips/unstable): FTBFS: use -O2 for mipsen?

Package: gcc-snapshot Version: 20030531-2 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-snapshot_20030531-2 on resume.rfc822.org by > sbuild/mips 1.170 > Build started at 20030601-1033 [...] > ** Using build dependencies supplied by packa

Bug#192576: gcc-3.2: 3.2/3.3 alpha: ICE while building libquicktime

Package: gcc-3.2 Version: 1:3.2.3-2 Severity: important confirmed with gcc-snapshot 20030410-1. gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include/quicktime -O3 -funroll-all-loops -fomit-frame-pointer -finline-functions -W -Wall -Wno-unused -Winline -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOU

Bug#192568: gcc-3.2: 3.2/3.3 alpha: ICE while building agistudio

Package: gcc-3.2 Version: 1:3.2.3-2 Severity: important confirmed with gcc-snapshot 20030410-1 and g++-2.95 2.95.4-17 g++ -c -pipe -Wall -W -g -D_REENTRANT -DQT_THREAD_SUPPORT -I/usr/include/qt3 -I/usr/include/qt -o wordsedit.o wordsedit.cpp wordsedit.cpp: In member function `void WordsEdit::mer

Bug#184753: gcc-3.2: [3.2/3.3 regression]: alpha ICE while building ddd/kseg

Package: gcc-3.2 Version: 1:3.2.3-0pre5 Severity: important g++ -c -fomit-frame-pointer -ffast-math -g -O2 -I/usr/share/qt3/include KSegProperties.cpp KSegProperties.cpp:31: Internal compiler error in mem_loc_descriptor, at dwarf2out.c:7903 if g++ -DIGNORED_YYSTYPE=int -DHAVE_CONFIG_H -I. -I

Bug#184749: gcc-3.2: alpha: ICE while building swi-prolog-packages

Package: gcc-3.2 Version: 1:3.2.3-0pre5 Severity: important gcc -c -Wall -O2 -fno-strict-aliasing -I. -I../src -I/usr/include -fPIC -funsigned-char -DHAVE_CONFIG_H evt/event.c -o evt/event.o evt/event.c: In function `getTimeEvent': evt/event.c:235: Internal compiler error in simplify_unary_opera

Bug#184684: gcc-3.2: [3.2/3.3 regression] powerpc: ICE while building rscheme

Package: gcc-3.2 Version: 1:3.2.3-0pre5 Severity: important longint.c: In function `int_64_neg': longint.c:259: error: could not split insn (insn:TI 81 10 63 (nil) (set (reg:SI 11 r11) (const_int 4294901760 [0x])) 300 {*movsi_internal1} (insn_list:REG_DEP_ANTI 33 (insn_list:REG_DE

Re: Processed: reassign 179781 to glibc, severity of 179781 is serious, merging 179781 178645

h has been hidden. We are putting the compat symbols in glibc, rather than every library that might have linked with a libgcc symbol. All of the merged bugs are caused by this problem. I don't see how you can understand that #178645 is a glibc problem, but not #179781. They are the same problem, with different symbols from the same library. -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own. pgpCXtsMRXitB.pgp Description: PGP signature

Bug#179161: [fixed in snapshot 20030105] lcdproc_0.4.3-12(mipsel) regression from 2.95

Package: gcc-3.2 Version: 1:3.2.2-0pre7 Severity: important There was an error while trying to autobuild your package: > Automatic build of lcdproc_0.4.3-12 on repeat.rfc822.org by sbuild/mipsel > 1.170 > Build started at 20030111-2236 [...] > ** Using build dependencies supplied by package: >

Bug#176311: gcc-3.2: configure generated from broken libtool.m4

On Fri, Jan 24, 2003 at 10:08:36PM +0100, Andreas Schwab wrote: > [EMAIL PROTECTED] (Ryan Murray) writes: > > |> The branch of libtool that supports --tag has been totally untouched > |> in cvs for at least two years. > > The multi-language-branch is dead, and has been

Bug#176311: gcc-3.2: configure generated from broken libtool.m4

> I think you'll get more traction if you do this on a per-directory > basis: libstdc++-v3, libjava, etc all separated out. Not possible. Everything uses the top level libtool.m4. They either all match, or it's not going to build. -- Ryan Murray, Debian Developer ([EMAIL P

Bug#176311: gcc-3.2: configure generated from broken libtool.m4

On Fri, Jan 24, 2003 at 05:27:45PM +0100, Franz Sirl wrote: > >Ryan Murray provided a patch, which I attach here. Needed for the 3.3 > >branch as well. checked on mips{,el}-linux and i386-linux only. > > > >The patch touches a few Makefile.am's to remove the > &

Bug#176311: gcc-3.2: configure generated from broken libtool.m4

On Fri, Jan 24, 2003 at 08:57:08AM +0100, Matthias Klose wrote: > Benjamin Kosnik writes: > > On Sun, 12 Jan 2003 11:25:04 +0100 > > Matthias Klose <[EMAIL PROTECTED]> wrote: > > > > >Is it likely this will be addressed in the gcc-3.2 branch? > >

Bug#176311: gcc-3.2: configure generated from broken libtool.m4

Package: gcc-3.2 Version: 1:3.2.2ds4-0pre5 Severity: grave The version of libtool used to build this source package is too old to correctly support shared libraries for the Debian mips and mipsel architectures. At least version (1.4.2-7) and higher correctly supports them. You need to update all

Bug#84935: additional information needed for aptitude build failure on mips

ld without optimization. > Closing the report, if no further information is sent. We'll see after the transition starts whether or not it's still present. -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own. pgpve85yqcwlC.pgp Description: PGP signature

Bug#169497: G++ 3.2 breakage on sparc

el. > bug before we can begin the gcc-3.2/g++-3.2 transition. So the safe > way seems to be to build the C compiler twice to provide a 64bit > compiler for sparc. Anyone on debian-sparc to take care of that or fix I don't think we should start the transition until the compiler is fi

Bug#168888: two part bug

reassign 16 glibc clone 16 -1 reassign -1 gcc-3.2 retitle 16 sparc: libm has long double versions of math fx, but no prototypes retitle -1 libstdc++ configure check broken thanks #16 will continue to be for the glibc problem of the prototypes not being defined, but the functions e

Bug#168888: G++ 3.2 breakage on sparc

n arch specific # c++config.h, like it has an arch specific mathdef.h However, all of these functions do exist in libm.so.6, so perhaps the sparc specific bits/mathdef.h should be removed instead? Ben? What should we do with this? -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own. pgpVFkCTPNCES.pgp Description: PGP signature

Bug#161967: gcc-3.0_1:3.0.4ds3-13(powerpc/unstable): FTBFS

Package: gcc-3.0 Version: 1:3.0.4ds3-13 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_1:3.0.4ds3-13 on voltaire by sbuild/powerpc 1.169 > Build started at 20020921-1833 [...] > ** Using build dependencies supplied by package: > Build-D

Bug#155311: gcc-3.1_1:3.1.1ds3-1(powerpc/unstable): nof libraries missing?

Package: gcc-3.1 Version: 1:3.1.1ds3-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.1_1:3.1.1ds3-1 on voltaire by sbuild/powerpc 1.169 > Build started at 20020801-0144 [...] > ** Using build dependencies supplied by package: > Build-Dep

Bug#153696: gcc-3.0_1:3.0.4ds3-11(alpha/unstable): FTBFS: Invalid build-depends

Package: gcc-3.0 Version: 1:3.0.4ds3-11 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_1:3.0.4ds3-11 on lully by sbuild/alpha 1.169 > Build started at 20020720-1328 [...] > ** Using build dependencies supplied by package: > Build-Depend

Re: bootstrap/2987: gcc 3.0 0526 fails to build on mips*-linux

x27;s the way it was at that point in time. > And try again with the 3.1 prerelease. No one is going to > do anything with 3.0. And it's been fixed for some time in 3.0...not when it was originally changed to fixed, but soon afterwards...20020331 cvs of the 3.1 branch build

fixed in 3.0

reassign 128367 g++-2.95 thanks This is c++/4234: State-Changed-From-To: open->closed State-Changed-By: lerdsuwa State-Changed-When: Fri Nov 16 23:55:34 2001 Stat

Bug#131977: gcc-3.0_1:3.0.4ds0-0pre020127(powerpc/unstable): patch fails to apply

Package: gcc-3.0 Version: 1:3.0.4ds0-0pre020127 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_1:3.0.4ds0-0pre020127 on voltaire by > sbuild/powerpc 1.159 > Build started at 20020129-2009 [...] > ** Using build dependencies supplied by

Bug#117503: gcc-3.0_1:3.0.2ds4-2(mipsel/unstable): libffi isn't built, but packages think so?

Package: gcc-3.0 Version: 1:3.0.2ds4-2 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_1:3.0.2ds4-2 on repeat.rfc822.org by sbuild/mipsel > 1.159 > Build started at 20011028-2340 [...] > ** Using build dependencies supplied by package:

Bug#112462: gcc-3.0_1:3.0.2ds1-0pre010908(unstable): fails to build on mips{,el}

Package: gcc-3.0 Version: 1:3.0.2ds1-0pre010908 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_1:3.0.2ds1-0pre010908 on repeat.rfc822.org by > sbuild/mipsel 1.159 > Build started at 20010915-2056 [...] > ** Using build dependencies sup

Bug#110191: gcc-2.95_2.95.4.ds4-0.010825(unstable):

Package: gcc-2.95 Version: 2.95.4.ds4-0.010825 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-2.95_2.95.4.ds4-0.010825 on remake.rfc822.org by > sbuild/mipsel 1.159 > Build started at 20010825-2235 [...] > ** Using build dependencies suppl

Bug#110189: gcc-3.0_1:3.0.2ds0-0pre010825(unstable): outdated build-depends

Package: gcc-3.0 Version: 1:3.0.2ds0-0pre010825 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_1:3.0.2ds0-0pre010825 on resume.rfc822.org by > sbuild/mips 1.159 > Build started at 20010826-0710 [...] > ** Using build dependencies suppl

Bug#109718: in addition...

In addition to the previous conflicts line, gcc-3.0-nof depends on gcc-base, which doesn't exist. Should probably be gcc-3.0-base -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own.

Bug#109718: gcc-3.0: incorrect Conflicts: line

Package: gcc-3.0 Version: 1:3.0.1-0pre010811 Severity: normal gcc-3.0 has an invalid Conflicts: on alpha: Conflicts: libc5-dev, egcc (<< EGCS_FIRST_PRIMARY)

Bug#107191: libgc on mips, mipsel, and m68k

libgc5 is available on mips, mipsel, and m68k now, and should be usable.

Bug#107012: gcc-3.0_1:3.0.1ds0-0pre010727(unstable): fails to build from source

Package: gcc-3.0 Version: 1:3.0.1ds0-0pre010727 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_1:3.0.1ds0-0pre010727 on resume.rfc822.org by > sbuild/mips 1.159 > Build started at 20010729-0319 [...] > ** Using build dependencies suppl

Bug#101570: gcc-3.0_3.0.ds9-1(unstable):

Package: gcc-3.0 Version: 3.0.ds9-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of gcc-3.0_3.0.ds9-1 on resume.rfc822.org by sbuild/mips 1.158 > Build started at 20010620-0013 [...] > ** Using build dependencies supplied by package: > Build-Dep

Re: Log for failed build of gcc-2.95_2.95.4.ds2-0.010522

On Mon, May 28, 2001 at 07:07:55PM +0200, Matthias Klose wrote: > Ryan Murray writes: > > gcc 2.95 fails to build on mips: > > ok, debian/patches/gcc-mips-linux.dpatch didn't call autoconf. Please > could you retry with the appended updated patch and autoconf2.13 &

oh, and the build log...

here's the full build log of the failed build -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own. mips-gcc.log.bz2 Description: Binary data pgpR6EYIWEHi9.pgp Description: PGP signature

Log for failed build of gcc-2.95_2.95.4.ds2-0.010522

sembly in some cases. -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own. pgpV0VVdhvnM0.pgp Description: PGP signature

Bug#97769: gcc-2.95: missing build dependency

Package: gcc-2.95 Version: 1:2.95.4-0.010506 Severity: serious make check needs libncurses5-dev installed: make[7]: Entering directory `/build/buildd/gcc-2.95-2.95.4.ds1/build-native/mips-linux/libg++/etc/lf' ... /build/buildd/gcc-2.95-2.95.4.ds1/src-native/libg++/etc/lf/screen.cc:5:termcap.h: N

Bug#92153: gcc-2.95: fails to build

Package: gcc-2.95 Version: 1:2.95.3-9 Severity: serious gcc-2.95 fails to build on at least mips and sparc with: dh_installchangelogs -a -Nprotoize-2.95-arch-% -Nlibstdc++2.10-dev-arch-% \ -Nlibg++2.8.1.3-dev-arch-% -Nlibstdc++2.10-dbg-arch-% -Nlibg++2.8.1.3-dbg-arch-% -Ngcc-2.95 -Ncpp-2.