Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Aug 2018 16:40:58 +0200
From:      Jan Beich <jbeich@FreeBSD.org>
To:        Alexander Evdokimov <xpro2004@gmail.com>
Cc:        office@freebsd.org
Subject:   Re: icu 62.1_2,1 compile error
Message-ID:  <8t4t-mbr9-wny@FreeBSD.org>
In-Reply-To: <CAC6fAsMzwv2ea_Jqk1feg1%2B8g3-=7bE2oSACxj5RwkpsV9tQOA@mail.gmail.com> (Alexander Evdokimov's message of "Sat, 25 Aug 2018 11:57:50 %2B0300")
References:  <CAC6fAsMzwv2ea_Jqk1feg1%2B8g3-=7bE2oSACxj5RwkpsV9tQOA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Evdokimov <xpro2004@gmail.com> writes:

> Hello,
>
> We can't update any packagies depended on ICU, because of icu compile
> error. Please, help.
> uname -a
> FreeBSD db.x-pro.ru 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789 amd64

10.0-RELEASE reached EOL on 2015-02-28. As of /stable/10 in-base toolchain
remains one of major contributors to planned obsolescence. Not much you can
do other than upgrade to a supported FreeBSD version[1] or switch the ports
tree to a revision close to the EOL date.

[1] https://www.freebsd.org/security/#sup



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8t4t-mbr9-wny>