Re: [arch-general] [arch-dev-public] Kill old gcc versions
Jan de Groot wrote:
On Sun, 2009-06-14 at 19:06 +0200, Thomas Bächler wrote:
Can we kill gcc3 and gcc34 from extra? We used to need them for qemu, but that's fixed, so they're useless. Objections?
Move it to AUR. We don't need these anymore.
virtualbox recommendation are gcc3.3 or later except for the GCC 4.0.x series). GCC 4.3.3 is recommended. i've tried to compile with gcc 4.4.0 and is failing. i suggest to move it to community because there are severals packages[1] that have in makedepends gcc34. [1] http://dpaste.com/55327/ -- Ionut
Biru Ionut wrote:
Jan de Groot wrote:
On Sun, 2009-06-14 at 19:06 +0200, Thomas Bächler wrote:
Can we kill gcc3 and gcc34 from extra? We used to need them for qemu, but that's fixed, so they're useless. Objections?
Move it to AUR. We don't need these anymore.
virtualbox recommendation are gcc3.3 or later except for the GCC 4.0.x series). GCC 4.3.3 is recommended. i've tried to compile with gcc 4.4.0 and is failing. i suggest to move it to community because there are severals packages[1] that have in makedepends gcc34.
wrong list: http://dpaste.com/55329/ -- Ionut
Biru Ionut schrieb:
Jan de Groot wrote:
On Sun, 2009-06-14 at 19:06 +0200, Thomas Bächler wrote:
Can we kill gcc3 and gcc34 from extra? We used to need them for qemu, but that's fixed, so they're useless. Objections?
Move it to AUR. We don't need these anymore.
virtualbox recommendation are gcc3.3 or later except for the GCC 4.0.x series). GCC 4.3.3 is recommended. i've tried to compile with gcc 4.4.0 and is failing. i suggest to move it to community because there are severals packages[1] that have in makedepends gcc34.
If you want this, let this go to aur-general. I am removing the packages from extra now, but I'll leave the PKGBUILDs in SVN trunk for now, so any TU who wants to adopt this or any AUR user who wants to add this can access them.
On Sun, 2009-06-14 at 21:23 +0200, Thomas Bächler wrote:
Biru Ionut schrieb:
Jan de Groot wrote:
On Sun, 2009-06-14 at 19:06 +0200, Thomas Bächler wrote:
Can we kill gcc3 and gcc34 from extra? We used to need them for qemu, but that's fixed, so they're useless. Objections?
Move it to AUR. We don't need these anymore.
virtualbox recommendation are gcc3.3 or later except for the GCC 4.0.x series). GCC 4.3.3 is recommended. i've tried to compile with gcc 4.4.0 and is failing. i suggest to move it to community because there are severals packages[1] that have in makedepends gcc34.
If you want this, let this go to aur-general. I am removing the packages from extra now, but I'll leave the PKGBUILDs in SVN trunk for now, so any TU who wants to adopt this or any AUR user who wants to add this can access them.
-1 from me IMHO I would like it to see them stay in extra For example : imlib which has errors compiling with gcc-4.4.0 compiles fine with gcc-3.4 just fixup the PKGBUILD like this: # $Id: PKGBUILD 356 2008-04-18 22:56:27Z aaron $ # Maintainer: dorphell <dorphell@archlinux.org> # Committer: Judd Vinet <jvinet@zeroflux.org> pkgname=imlib pkgver=1.9.15 pkgrel=4 pkgdesc="General image handling library for X11 and Gtk" arch=(i686 x86_64) url="http://www.enlightenment.org/Libraries/Imlib.html" license=('GPL') depends=(gtk libungif libpng libtiff libsm) makedepends=(gcc34) source=(http://ftp.gnome.org/pub/GNOME/sources/imlib/1.9/$pkgname-$pkgver.tar.bz2 debian-bug448360.patch CAN-2004-1026.patch aclocal-fixes.patch) options=(!libtool) md5sums=('7db987e6c52e4daf70d7d0f471238eae' '5f9da697934b6bd3b497ac9160ce4f5c' 'b273d36aa60adbfaacaf6062234e4c1f' '33b832f0dc6c9723cd0dfe9c8d0a6797') build() { cd $startdir/src/$pkgname-$pkgver patch -Np1 -i ${startdir}/src/debian-bug448360.patch || return 1 patch -Np1 -i ${startdir}/src/CAN-2004-1026.patch || return 1 patch -Np0 -i ${startdir}/src/aclocal-fixes.patch || return 1 ./configure --prefix=/usr --sysconfdir=/etc --enable-shm CC=/usr/bin/gcc-3.4 make || return 1 make DESTDIR=$startdir/pkg install } and it works
Baho Utot schrieb:
-1 from me
IMHO I would like it to see them stay in extra
For example : imlib which has errors compiling with gcc-4.4.0 compiles fine with gcc-3.4
Every normal package can be fixed to compile with the latest gcc, the right way is always to do that, not to stick to legacy compilers (besides, imlib must have built with 4.3.0, so the issue must be a minor non-standard-compliance in the code). qemu was an exception because its code generators relied on the way gcc3 generated the code. About virtualbox, it probably suffers from similar problems. But those are special cases - imlib is certainly no reason to keep a legacy compiler.
On Mon, 2009-06-15 at 00:13 +0200, Thomas Bächler wrote:
Baho Utot schrieb:
-1 from me
IMHO I would like it to see them stay in extra
For example : imlib which has errors compiling with gcc-4.4.0 compiles fine with gcc-3.4
Every normal package can be fixed to compile with the latest gcc, the right way is always to do that, not to stick to legacy compilers (besides, imlib must have built with 4.3.0, so the issue must be a minor non-standard-compliance in the code).
qemu was an exception because its code generators relied on the way gcc3 generated the code. About virtualbox, it probably suffers from similar problems. But those are special cases - imlib is certainly no reason to keep a legacy compiler.
I have encountered many packages in extra that don't compile with gcc-4.4.0. The easy way to fix them is to compile them with gcc-3.4
On Sun, 2009-06-14 at 18:46 -0400, Baho Utot wrote:
I have encountered many packages in extra that don't compile with gcc-4.4.0. The easy way to fix them is to compile them with gcc-3.4
The easy way to fix them is by reporting bugs. Bugfixing most of these packages is very easy and takes us only a few minutes to fix, so why bother supporting an old outdated compiler that hasn't been supported upstream for a long while?
On Mon, 2009-06-15 at 00:51 +0200, Jan de Groot wrote:
On Sun, 2009-06-14 at 18:46 -0400, Baho Utot wrote:
I have encountered many packages in extra that don't compile with gcc-4.4.0. The easy way to fix them is to compile them with gcc-3.4
The easy way to fix them is by reporting bugs. Bugfixing most of these packages is very easy and takes us only a few minutes to fix, so why bother supporting an old outdated compiler that hasn't been supported upstream for a long while?
Do you really want a list of all the packages in extra that are broke? There are lots of them
I'd have to agree with Jan on this one. The reason why packages don't compile on the with newer compilers is generally because the code is not standards compliant and needs fixing anyways. So the right thing to do is fix the broken packages in extra and move on. Then again, I'm not an Arch Linux developer, so that is easy for me to say. When I download some source tarball and try to compile it and it fails, I never go try it with and older compiler. If it is a application/library I really need, I patch it until it compiles. On Sun, Jun 14, 2009 at 6:17 PM, Baho Utot<baho-utot@columbus.rr.com> wrote:
On Mon, 2009-06-15 at 00:51 +0200, Jan de Groot wrote:
On Sun, 2009-06-14 at 18:46 -0400, Baho Utot wrote:
I have encountered many packages in extra that don't compile with gcc-4.4.0. The easy way to fix them is to compile them with gcc-3.4
The easy way to fix them is by reporting bugs. Bugfixing most of these packages is very easy and takes us only a few minutes to fix, so why bother supporting an old outdated compiler that hasn't been supported upstream for a long while?
Do you really want a list of all the packages in extra that are broke?
There are lots of them
On Sun, 2009-06-14 at 18:43 -0500, Dwight Schauer wrote:
I'd have to agree with Jan on this one. The reason why packages don't compile on the with newer compilers is generally because the code is not standards compliant and needs fixing anyways. So the right thing to do is fix the broken packages in extra and move on. Then again, I'm not an Arch Linux developer, so that is easy for me to say.
When I download some source tarball and try to compile it and it fails, I never go try it with and older compiler. If it is a application/library I really need, I patch it until it compiles.
On Sun, Jun 14, 2009 at 6:17 PM, Baho Utot<baho-utot@columbus.rr.com> wrote:
On Mon, 2009-06-15 at 00:51 +0200, Jan de Groot wrote:
On Sun, 2009-06-14 at 18:46 -0400, Baho Utot wrote:
I have encountered many packages in extra that don't compile with gcc-4.4.0. The easy way to fix them is to compile them with gcc-3.4
The easy way to fix them is by reporting bugs. Bugfixing most of these packages is very easy and takes us only a few minutes to fix, so why bother supporting an old outdated compiler that hasn't been supported upstream for a long while?
Do you really want a list of all the packages in extra that are broke?
There are lots of them
Normally I would agree with you but I have about 40 that don't build and I have about 85 others that I have not looked at that don't build
Baho Utot wrote:
On Mon, 2009-06-15 at 00:51 +0200, Jan de Groot wrote:
On Sun, 2009-06-14 at 18:46 -0400, Baho Utot wrote:
I have encountered many packages in extra that don't compile with gcc-4.4.0. The easy way to fix them is to compile them with gcc-3.4
The easy way to fix them is by reporting bugs. Bugfixing most of these packages is very easy and takes us only a few minutes to fix, so why bother supporting an old outdated compiler that hasn't been supported upstream for a long while?
Do you really want a list of all the packages in extra that are broke?
There are lots of them
Filing a bug report means they will get fixed. Not telling us about them, means they will wait until an update or rebuild is needed. Allan
On Sun, 2009-06-14 at 21:23 +0200, Thomas Bächler wrote:
Biru Ionut schrieb:
Jan de Groot wrote:
On Sun, 2009-06-14 at 19:06 +0200, Thomas Bächler wrote:
Can we kill gcc3 and gcc34 from extra? We used to need them for qemu, but that's fixed, so they're useless. Objections?
Move it to AUR. We don't need these anymore.
virtualbox recommendation are gcc3.3 or later except for the GCC 4.0.x series). GCC 4.3.3 is recommended. i've tried to compile with gcc 4.4.0 and is failing. i suggest to move it to community because there are severals packages[1] that have in makedepends gcc34.
If you want this, let this go to aur-general. I am removing the packages from extra now, but I'll leave the PKGBUILDs in SVN trunk for now, so any TU who wants to adopt this or any AUR user who wants to add this can access them.
I adopted it and put it in AUR: http://aur.archlinux.org/packages.php?ID=27768
participants (7)
-
Allan McRae
-
Baho Utot
-
Biru Ionut
-
Dwight Schauer
-
Jan de Groot
-
Jordy van Wolferen
-
Thomas Bächler