Subject: Re: gcc 2.95.3 issue
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 11/23/2003 10:11:37
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.95.3?
> 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 errors
> on loop.c (I can try it again and post the errors, but I don't see why it is
> now set to require 2.95.3 in -current/i386 when so much work was put into
> switching -current to 3.3.x.
> Is there a workaround? I have 412 packages installed, probably half of which
> 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
See mk/compiler.mk rev. 1.22.