Re: HEADS UP: ports/ and 10.0-CURRENT


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!
>>>
>>> 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
>>
> 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.
>
> Regards,
> Oliver
>
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!

Thanks all

Matt
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"