HEADS UP: ports/ and 10.0-CURRENT

Doug Barton dougb at FreeBSD.org
Wed Sep 28 20:49:33 UTC 2011


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.



-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/



More information about the freebsd-current mailing list