[MacPorts] #40771: vaucanson 2
MacPorts
noreply at macports.org
Tue Nov 12 01:54:19 PST 2013
#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 akim.demaille@…):
Replying to [comment:9 ryandesign@…]:
Hi Ryan,
> 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?
> You've blacklisted Xcode clang, but the version in Xcode 5.0.1 on
Mavericks seemed to build it just fine. So I think you should be more
selective and blacklist only those versions of Xcode clang that are
unsuitable, using the compiler_blacklist_versions portgroup.
XcodeVersionInfo shows the versions of Xcode clang that we know about. If
you know a version of Xcode clang that fails to build it, then we can try
to narrow it down from there.
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? I had written:
{{{
# We need C++11 support, provided by G++ 4.8+ and Clang++ 3.3+.
compiler.blacklist cc \
*dragonegg* \
*clang \
*clang-2.* \
{*clang-3.[012]} \
*gcc \
*gcc-3.* \
{*gcc-4.[0-7]}
}}}
If I read correctly your answer, this should suffice?
{{{
# We need C++11 support, provided by G++ 4.8+ and Clang++ 3.3+.
compiler.blacklist *dragonegg* \
*clang-2.* \
{*clang-3.[012]} \
*gcc-3.* \
{*gcc-4.[0-7]}
}}}
Thanks for the detailed answers.
--
Ticket URL: <https://trac.macports.org/ticket/40771#comment:12>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list