lvm-3.3 problem with sierra

Chris Jones jonesc at hep.phy.cam.ac.uk
Sun Oct 9 18:49:40 CEST 2016


P.s. When sending a log file as an attachment please give the file name a proper suffix, .txt, as without this email readers often do not know what to do with it. The right extension makes it possible to view on iOS for instance.... 

> On 9 Oct 2016, at 5:47 pm, Chris Jones <jonesc at hep.phy.cam.ac.uk> wrote:
> 
> Hi,
> 
>> On 9 Oct 2016, at 2:13 pm, Comer Duncan <comer.duncan at gmail.com> wrote:
>> 
>> I tried to follow the upgrade procedure and eventually got the complaint that lvm-3.3 is not supported. I'm attaching the log file and ask for  advice about ways around this obstacle. Thanks for your help!
> 
> Personally i don't quite follow the migration guide word for word, as when reinstalling I prefer, instead of just blindly reinstalling everything as it was, going through the list by hand and deciding what I really still want.
> 
> In this case if you have explicitly installed llvm, or clang, 3.3 then do not try and reinstall it and pick a newer version. If it is being pulled in as a dependency of some other port, check that port to see if it has other variants you can use instead. Almost certainly all ports that needs an llvm/clang version installed will actually be using something a lot newer than 3.3 now. 
> 
> Chris
> 
>> 
>> Comer
>> <Sierralogfile>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users




More information about the macports-users mailing list