Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Nov 2018 00:41:47 +0100
From:      Miroslav Lachman <000.fbsd@quip.cz>
To:        Niclas Zeising <zeising+freebsd@daemonic.se>, Dimitry Andric <dim@FreeBSD.org>
Cc:        ports@freebsd.org
Subject:   Re: devel/llvm60 build failure in poudriere
Message-ID:  <7b4c2edc-3e85-bf55-abf5-3b768154cb12@quip.cz>
In-Reply-To: <9a2001c1-ec41-fbc4-2b2a-6057950a187f@daemonic.se>
References:  <2c09b23e-50f2-019c-e420-f597c8ab8637@quip.cz> <F620E5ED-1879-4D1C-ACA4-50A2AE9873CC@FreeBSD.org> <89648619-7b91-1df8-16b9-d94dae4befd9@quip.cz> <9a2001c1-ec41-fbc4-2b2a-6057950a187f@daemonic.se>

next in thread | previous in thread | raw e-mail | index | archive | help
Niclas Zeising wrote on 2018/11/03 19:14:
> On 11/2/18 12:39 PM, Miroslav Lachman wrote:
>> Dimitry Andric wrote on 2018/11/02 08:26:
>>> You should first check whether your ports tree is cleanly checked out,
>>> revert any local changes, and then try again.  If that fails too, delete
>>> the ports tree, and check it out from scratch.
>>
>> Update of ports/Mk fixed the problem with llvm60 but it breaks 40+ 
>> other ports dependent on old xorgproto. It seems I cannot update just 
>> iridium and firefox.
>>
> 
> xorgproto has replaced all the old *proto ports.  You need to update 
> that part of the tree if you are updating bsd.xorg.mk.  Remember, 
> howerver, that having different parts of the ports tree at different 
> versions is a recipe  for disaster.

Yes, I know it. That's why I gave up and will stay on old versions of 
iridium and firefox until I will have time to prepare and test (in 
virtualbox) the update of all 1500+ installed packages on my desktop 
(PC-BSD based)

Thanks anyway

Miroslav Lachman



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7b4c2edc-3e85-bf55-abf5-3b768154cb12>