clang 3.4 can't be configured (part of a selfupdate)

Ken Cunningham ken.cunningham.webuse at gmail.com
Fri Jul 29 08:56:25 PDT 2016


On 2016-07-29, at 7:57 AM, [ftp83plus] wrote:

> SoI would have to 0- remove said files 1- reinstall MacPorts,

Yes

> 2- correct the macports.conf to replace x86 by x86_64 architecture

No, don't think so. My macports.conf has 

build_arch         x86_64

near the top -- I installed macports two years ago. I can't recall at the moment if I added that at some point in the past, or if macports did that on the install. I think macports did it...

> 
> But how would I know if the macports.conf contains the correct data?

Leave it as macports installed it.


> What should be the default for variants.conf?

/opt/local/etc/macports/variants.conf.default


> And why would it use clang-3.3 when it's explicitly told to use clang 3.4?


Most likely because clang-3.3 was still around somehow, and clang-3.4 was not.

This should not be the case when you do a clean install.



Hope this is helpful and not confusing.

Ken




More information about the macports-users mailing list