#40771: vaucanson 2 ------------------------------+-------------------------------- Reporter: akim.demaille@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: vaucanson | ------------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [comment:12 akim.demaille@…]:
I had to change the `master_sites` to http://www- old.lrde.epita.fr/dload/vaucanson/2.0/ to get the file to download.
That's weird. The original link seems to work just as well as this one. What failure did you face?
Can't reproduce it now! :)
I need clang 3.3 or better, but on my machine "clang" is 3.2. How can I fine tune by compiler black-list to be sure that when I accept clang, it's really 3.3 or newer? I thought this was globbing on compiler names, but is it better than that?
Yes, compiler.blacklist operates on MacPorts compiler names. The MacPorts compiler name of Xcode's clang is always "clang" regardless of what version it is, hence the problem. That's why we wrote the compiler_blacklist_versions portgroup to let you blacklist on a finer grain, based on the version number of the compiler. Note that Xcode's clang is Apple's LLVM compiler, which is based on the open source clang, but does not use the same version numbers. In r113207 I already included this portgroup to blacklisting Xcode clang versions older than Apple's build number 500, which is what Xcode 5 includes. Perhaps slightly older versions of Xcode clang might work also and we can amend this directive if so. -- Ticket URL: <https://trac.macports.org/ticket/40771#comment:15> MacPorts <http://www.macports.org/> Ports system for OS X