Subject: Re: gcc 2.95.3 issue
To: None <email@example.com>
From: Sean Davis <firstname.lastname@example.org>
Date: 11/23/2003 05:24:04
Content-Type: text/plain; charset=us-ascii
On Sun, Nov 23, 2003 at 10:11:37AM +0100, email@example.com wrote:
> On Sat, Nov 22, 2003 at 10:58:08PM -0500, Sean Davis wrote:
> > Okay, I know pkgsrc is/was frozen for "stability fixes for branching" or
> > some such, but why does every package I try to build now require gcc 2.=
> > Shouldn't that particular change have been made on the branch?
> > pkgsrc's gcc 2.95.3nb<whatever> doesn't even build, it dies with two er=
> > on loop.c (I can try it again and post the errors, but I don't see why =
> > now set to require 2.95.3 in -current/i386 when so much work was put in=
> > switching -current to 3.3.x.
> > Is there a workaround? I have 412 packages installed, probably half of =
> > are out of date, and I can't update any of them because of this.
> > This is -current as of oct 26 (1.6ZE), with pkgsrc as of earlier today.
> During a period of time, the version of gcc3 in -current was "3.3.2-nb1"
> which produced the observed behaviour. A fix for that was committed, but
> was removed last week since the -current gcc verson is now ok WRT both gcc
> and pkgsrc.
> See mk/compiler.mk rev. 1.22.
dive@eros:/usr/pkgsrc/mk % ident compiler.mk
$NetBSD: compiler.mk,v 1.23 2003/11/12 13:13:43 grant Exp $
The -current gcc version is not ok WRT pkgsrc, unless I need to update
-current for the fix in compiler.mk to take effect.
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (NetBSD)
-----END PGP SIGNATURE-----