Date: Wed, 28 Sep 2011 16:53:50 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Matt <sendtomatt@gmail.com> Cc: aakuusta@gmail.com, Doug Barton <dougb@FreeBSD.org>, "Hartmann, O." <ohartman@zedat.fu-berlin.de>, freebsd-ports@freebsd.org, freebsd-current@freebsd.org Subject: Re: HEADS UP: ports/ and 10.0-CURRENT Message-ID: <B89AE452-4F8F-4364-9219-B260EEAB66FF@gmail.com> In-Reply-To: <4E83AF81.7080708@gmail.com> References: <20110926230335.041fd9aa@lab.lovett.com> <CAN6yY1t5wJ3%2B4LG=upL6sR7tSNU6Uhx-y=L0AJm6rKFsKnvPiQ@mail.gmail.com> <86mxdqfq69.fsf@gmail.com> <4E818941.7060006@zedat.fu-berlin.de> <CAF6rxg=N4GKM7h_HGMcEMYQf_50TSEmPdywD0A%2BkBJBaGNvfYA@mail.gmail.com> <4e83255b.g7c%2BBRfF0FDmiYc%2B%perryh@pluto.rain.com> <4E82CC34.4070305@zedat.fu-berlin.de> <4E835988.8060702@zedat.fu-berlin.de> <86k48sr1f7.fsf@gmail.com> <4E83699E.7010101@zedat.fu-berlin.de> <3DF52192-E4D3-47F4-B41F-5D685F933AE0@gmail.com> <4E836DEE.2080608@zedat.fu-berlin.de> <4E837292.3000207@zedat.fu-berlin.de> <4E8375E2.5040407@gmail.com> <4E8377F1.7020906@zedat.fu-berlin.de> <4E838127.5090601@FreeBSD.org> <4E83A2AC.2080204@zedat.fu-berlin.de> <4E83AF81.7080708@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 28, 2011, at 4:36 PM, Matt wrote: > On 09/28/11 15:41, Hartmann, O. wrote: >> On 09/28/11 22:18, 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! >>>>=20 >>>> This is a catastrophy ... >>>>=20 >>>> 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. >>>=20 >>> Solutions are to set UNAME_r=3D9.0-CURRENT in your environment, = and/or >>> twiddle the version in newvers.sh and rebuild/reinstall your kernel. >>>=20 >>>=20 >>> hth, >>>=20 >>> Doug >>>=20 >> Yes, it has been discussed. But I was too dumb to realise that the >> phenomenon I >> experienced was triggered by this. >> I'll stay tuned and watch when a solution is at hand. >>=20 > I also was apparently too dumb! Making progress with UNAME_r and = newvers.sh as we speak. > I was unable to compile neon29 properly with UNAME_r alone... = buildkernel underway. > At least it's never boring! Please be aware that some user apps like net-smp and kernel = modules like nvidia-driver key in on the __FreeBSD_version number. So if = it's out of sync with reality, bad things can happen as you're breaking = some developers' assumptions. Thanks! -Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B89AE452-4F8F-4364-9219-B260EEAB66FF>