Date: Wed, 28 Sep 2011 12:53:23 -0800 From: Beech Rintoul <beech@freebsd.org> To: Doug Barton <dougb@freebsd.org> Cc: Matt <sendtomatt@gmail.com>, Garrett Cooper <yanegomi@gmail.com>, freebsd-current@freebsd.org, freebsd-ports@freebsd.org, aakuusta@gmail.com, "Hartmann, O." <ohartman@zedat.fu-berlin.de> Subject: Re: HEADS UP: ports/ and 10.0-CURRENT Message-ID: <201109281253.23407.beech@freebsd.org> In-Reply-To: <4E8387F6.7060709@FreeBSD.org> References: <20110926230335.041fd9aa@lab.lovett.com> <201109281245.40015.beech@freebsd.org> <4E8387F6.7060709@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 28 September 2011 12:47:50 Doug Barton wrote: > On 09/28/2011 13:45, Beech Rintoul wrote: > > On Wednesday 28 September 2011 12:18:47 Doug Barton wrote: > >> On 09/28/2011 12:39, Hartmann, O. wrote: > >>> The mess started to happen when I tried to "repair" a non CLANG > >>> compiling port math/gotoblas with portmaster -vf amth/gotoblas. > >>> Since this build binutils and even gettext and libiconv, I guess they > >>> got broken. Last I saw was a successful installation report from > >>> portmaster. But the libiconv.so.3 wasn't there anymore when I checked! > >>> > >>> This is a catastrophy ... > >>> > >>> I'm on FreeBSD 10.0-CURRENT r225844 > >> > >> It's been widely reported on the ports list that you can't do fresh > >> ports compiles on 10-current, and won't be able to until well after > >> 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand > >> the 2-digit release version. > >> > >> Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or > >> twiddle the version in newvers.sh and rebuild/reinstall your kernel. > >> > >> > >> hth, > >> > >> Doug > > > > So if I change /usr/src/sys/conf/newvers.sh to something like vers 9.9 > > I'm not going to shoot myself in the foot if I try and update? I would > > really like to avoid downgrading this box.I've altready been bitten once > > today and had to build packages on my tindy and force install. > > That should be the case, yes. I haven't tested it yet myself. If you do, > and it works, let us know and I'll write the UPDATING entry if no one > else does. No problem, I'm building now. Any suggestions as to what port I should try after the reboot? Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html ---------------------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201109281253.23407.beech>