don't really care "whose fault it is".
>
Too late for me, I was very happy with my FreeBSD-4.5
I think that it is not safe to go to CURRENT, but If you use it for
testing
purposes, then "good luck" :)
> But thanks for clarifying. I'll be sure to explain m
On Thu, 06 Jun 2002 10:14:52 MST, "David O'Brien" wrote:
> > There are still issues with the C++ compiler in the base system that
> > make building X and some other C++ ports tricky.
>
> There is no issue with the C++ compiler. There is issue with the X
> source that uses depreciated features
On Wed, Jun 05, 2002 at 08:46:59AM +, Christopher Nehren wrote:
> I've been monitoring the -CURRENT mailing list for about a day or two,
> and haven't seen anything that's really broken (except for GCC 3.x,
> which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
> TIA for the
On Thu, Jun 06, 2002 at 10:54:15AM +0200, Sheldon Hearn wrote:
> > I've been monitoring the -CURRENT mailing list for about a day or two,
> > and haven't seen anything that's really broken (except for GCC 3.x,
> > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
> > TIA for
÷ Thu, 06.06.2002, × 12:54, Sheldon Hearn ÎÁÐÉÓÁÌ:
> > I've been monitoring the -CURRENT mailing list for about a day or two,
> > and haven't seen anything that's really broken (except for GCC 3.x,
> > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
> > TIA for the info,
>
On 05 Jun 2002 08:46:59 GMT, Christopher Nehren wrote:
> I've been monitoring the -CURRENT mailing list for about a day or two,
> and haven't seen anything that's really broken (except for GCC 3.x,
> which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
> TIA for the info,
> C
On Wed, Jun 05, 2002 at 08:46:59AM +, Christopher Nehren wrote:
> I've been monitoring the -CURRENT mailing list for about a day or two,
> and haven't seen anything that's really broken (except for GCC 3.x,
> which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
> TIA for the
I've been monitoring the -CURRENT mailing list for about a day or two,
and haven't seen anything that's really broken (except for GCC 3.x,
which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
TIA for the info,
Chris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
I've been monitoring the -CURRENT mailing list for about a day or two,
and haven't seen anything that's really broken (except for GCC 3.x,
which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet?
TIA for the info,
Chris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubsc
