Bug#782444: libgccjit tests fail on kfreebsd and hang the buildds

On Sun, Apr 12, 2015 at 01:34:16PM +0200, Matthias Klose wrote: > Package: src:gcc-5 > Version: 5-20150410-1 > Severity: important > > the libgccjit tests fail on kfreebsd, hang the buildds, and get killed with a > timeout. Please see the build logs. As a workaround, I'll disable running > these

Bug#615157: Using -Werror in CFLAGS for a debian package build

Hi -devel, I was working on nbd-server upstream, and so had ran ./configure with CFLAGS='-Wall -Werror', which I consider good practice when writing C code. What I didn't notice immediately was that gcc was emitting some warnings, but that the -Werror option was not honored for those warnings. In

gdc-4.3_1:1.043-4.3.4-1 build on powerpc

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, You may want to investigate the gdc build on powerpc (see $SUBJECT for version). The compiler hit an ICE, but the build continued and dpkg thought it was successful. I signed it, since I know errors in a build's test suite are not unheard of withi

Bug#499998: cross-build: missing build-deps of libmpfr-dev and libgmp3-dev for host

Package: gcc-4.3 Version: 4.3.2-1 Severity: normal Hi, Subject says it all, really. When following the instructions in debian/README.cross, the build fails during a configure step where it complains it can't find libgmp3-dev and libmpfr-dev. Installing the host architecture's version of those pac

Bug#424855: Apply patches up to a specific patch

Package: gcc-4.2 Version: 4.2-20070405 Severity: wishlist Hi, Attached is a little makefile that will allow one to apply all patches in the Debian gcc package up to a named patch. Usage: make -f patch-Makefile PATCH_TO=m68k-save_pic patch-to-specific will apply all patches up to, but not inclu

Bug#381022: [m68k] gij fails trivial case

On Tue, Aug 01, 2006 at 07:13:22PM +0200, Matthias Klose wrote: > forcemerge 381022 312830 > tags 312830 + upstream > thanks > > needs either a more complete port of libffi for m68k (support for > closures) or a bug fix in stack unwinding (I did send Wouter a URL to > a patch that might be interes

Bug#380251: Building cross-compilers

Package: gcc-4.1 Version: 4.1.1-9 Severity: minor Hi, I'm currently trying to build cross-compilers on my system. I found two issues: * Following the guidelines in debian/README.cross does not work; a plain "dpkg-buildpackage" calls debian/rules clean, which regenerates debian/control for a

Bug#321486: Errr...

You tag this "moreinfo" yesterday, and before I have the time to provide that extra information, you close it? Can I disregard that moreinfo tag, or should I reopen the bug? -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROT

Bug#359281: tag forward?

Upstream PR 26415 mentions this bug, and at the very least is related, if it's not the same bug. Perhaps mark this bug as forwarded? (if that's not considered a good idea, at least with this mail the upstream PR is marked now :-) -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", sta

Re: bits from the release team: release goals, python, X.org, amd64, timeline

[You had removed m68k-build from the Cc list. Was that on purpose?] On Tue, May 30, 2006 at 02:01:19PM -0700, Steve Langasek wrote: > BTW, can you tell me anything about the dip in > http://buildd.debian.org/stats/graph2-quarter-big.png for m68k? Seems to be > heading in the wrong direction again

Re: bits from the release team: release goals, python, X.org, amd64, timeline

On Tue, May 30, 2006 at 12:05:26PM +0200, Andreas Barth wrote: > Timeline > > > Now, let's please take a more detailed look at the time line: > > > Thu 15 Jun 06: > > last chance to switch to gcc 4.1, python 2.4 > review architectures one more time > last

Bug#367657: GCC new warnings and compatibility

On Wed, May 17, 2006 at 09:54:56PM +0200, Wouter Verhelst wrote: > In configure.ac: > > AC_ARG_ENABLE(warnings-as-errors, > AC_HELP_STRING(--enable-warnings-as-errors,Treat warnings as errors > (default off), > [WARN_IS_ERR="$enableval"], [WARN_IS_ERR=&qu

Bug#367657: GCC new warnings and compatibility

On Wed, May 17, 2006 at 03:14:04PM +0100, Ian Jackson wrote: > Furthermore, because GCC has traditionally had such good warnings, and > such good configurability of warnings, and because no-one looks at > warnings that don't cause build failures, many people (myself > included) use -Werror in nearl

Re: qt4-x11

On Tue, Apr 25, 2006 at 09:47:19AM -0500, Stephen R Marenka wrote: > On Tue, Apr 25, 2006 at 08:31:07AM -0500, Stephen R Marenka wrote: > > On Tue, Apr 25, 2006 at 03:22:50PM +0200, Wouter Verhelst wrote: > > > qt4-x11 needs to be rebuilt on m68k, anything using it currently will

qt4-x11

Hi, qt4-x11 needs to be rebuilt on m68k, anything using it currently will give errors that libXcursor.la can't be found. Unfortunately, GCC 4.0 currently ICEs on QT4. Anyone know whether GCC 4.1 has the same issues? If not, should we proceed to build QT with GCC 4.1, or is that not advisable? -

Re: GCC 4.1 in experimental / GCC for etch

On Tue, Feb 21, 2006 at 11:34:55AM +0100, Aurelien Jarno wrote: > For m68k, the glibc does not build, gcc 4.0 segfault on system.c. It > looks like gcc 4.1 fixes the problem, but the resulting glibc has not > been tested. Many m68k ICEs are fixed by GCC 4.1. I intend to switch over quickstep (th

Re: cross compiler for i386 stable

On Mon, Jan 23, 2006 at 05:32:46PM +0100, Jörg Sommer wrote: > Hi, > > is it possible to build a cross compiler for sarge on i386 with the new > gcc-4.0? I've a powerpc with unstable and a i386 with stable, for which I > need to build some packages. Is this possible? I've been trying to do that,

Re: Building cross compilers

On Sun, Dec 11, 2005 at 09:49:14PM +0100, Daniel Widenfalk wrote: > Hi all, > > I'm trying to help Haakan Ardo with the toolchain-source package > and I'm having trouble building a cross compiler. First I must > say that I'm not yet 100% done with integrating the 4.0.3 line > of gcc into the toolc

Re: g++ insanity??????

Op vr, 02-12-2005 te 04:00 -0800, schreef Michael Blansfield: > Hello, > > I am trying to install the g++-3.3 compiler on my linux box. But I > need to install all the supporting libraries, which I do fine until I > get to libstdc++5-3.3-dev which requires g++! What is this? > Endless loop,

Bug#327780: Too hasty

reassign 327780 binutils found 327780 2.16.1cvs20050902-1 thanks Sorry, I was a bit too hasty. Current gcc is quite some time in the archive already, so it's unlikely it's at fault. Binutils, OTOH, has seen a recent upload. Downgrading it to the previous version indeed fixes the segfault issues.

Bug#327780: current gcc-4.0 is utterly useless on m68k

Package: gcc-4.0 Version: 4.0.1-6 Severity: grave Justification: renders package unusable Hi, Script started on Mon Sep 12 08:22:21 2005 [EMAIL PROTECTED]: /home/wouter~$ cat >foo.c int main() { ; return 0; } [EMAIL PROTECTED]:~$ gcc -o foo foo.c [EMAIL PROTECTED]:~$ ./foo Segmentation fault [EMA

Bug#321415: Bug#320038: gcc-4.0: ICE when building faust

On Wed, Sep 07, 2005 at 11:45:03PM +0200, Falk Hueffner wrote: > tags 320038 + moreinfo > thanks > > Hi, > > the gcc PR 23078 has been closed. Can you confirm the problem is gone > with a newer gcc snapshot? Both bugs talk about GCC 4.0.2. The Debian package is still 4.0.1 However, with gcc-sna

Bug#326002: [PR 23674] [m68k] ICE when compiling mlgmp

Package: gcc-4.0 Version: Hi, mlgmp failed to build on m68k due to an ICE with gcc-4.0 No issues when building with gcc-3.4 or gcc-snapshot. Upstream filed as PR 23674 -- The amount of time between slipping on the peel and landing on the pavement is precisely one bananosecond -- To UNSUBSC

Bug#321486: [m68k] ICE when trying to build boost

Package: gcc-4.0 Version: 4.0.1-3 Tags: fixed-upstream, upstream Hi, This one also only happens with gcc-4.0; gcc-3.4 and gcc-snapshot happily conclude where gcc-4.0 fails. As such, I haven't filed an upstream bug report -- The amount of time between slipping on the peel and landing on the pave

Bug#321438: [m68k] ICE when compiling gmp

Package: gcc-4.0 Version: 4.0.1-3 Tags: upstream, fixed-upstream Hi, gcc-4.0 produces an ICE on building gmp. It builds correctly with gcc-3.4, however. As it builds correctly with gcc-snapshot as well, I didn't bother filing an upstream bug. -- The amount of time between slipping on the peel

Bug#321415: [PR 23080][m68k] ICE on building blacs-mpi

Package: gcc-4.0 Version: 4.0.1-3 Tags: upstream Hi, GCC4 ICEs when trying to build blacs-mpi. Has been filed as upstream PR23080 a while ago already (but apparently something went wrong with the Debian bug I tried to file), and declared fixed there as well. Rg, -- The amount of time between s

Bug#320038: [PR23078][m68k] gcc-4.0: ICE when building faust

Package: gcc-4.0 Version: 4.0.0-2 There's an ICE when trying to build faust-0.9.3 on m68k. Upstream bug report: Regards, -- The amount of time between slipping on the peel and landing on the pavement is precisely one bananosecond -- To UNSU

Bug#228379: gcj: contains badly broken filename

3.3.1.gzGSKYOUt.gzbian.gzlder.claclassdapter.classslaompositeContext.classn.org> Source: python-gtk2 Version: 2.0.0-3 Replaces: python2.2-gtk2 (<< 1.99.17-4), python2.3-gtk2': File name too long if you need any further information, please let me know. -- Wouter Verhelst Debia