Subject: gcc 2.95.3 issue
To: None <firstname.lastname@example.org>
From: Sean Davis <email@example.com>
Date: 11/22/2003 22:58:08
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.
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!