#38389: hdf5-18: LLVM C11 support --------------------------+--------------------- Reporter: l@… | Owner: mmoll@… Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: C11 Port: hdf5-18 | --------------------------+--------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => mmoll@… Old description:

Hello,

For the C++ support for this port under Xcode if compiling with LLVM stdlib the flag -stdlib=libc++ is required if a project has been compiled with LLVM C11 support in Xcode. As such the following variant is necessary for the linker to not complain.

variant c11 description { Build with C11 support. } conflicts universal gcc44 gcc45 gcc46 gcc47 { configure.cxxflags -stdlib=libc++ }

Given that LLVM is the default compiler now, this should perhaps even be a default variant....

/Lasse

New description: Hello, For the C++ support for this port under Xcode if compiling with LLVM stdlib the flag -stdlib=libc++ is required if a project has been compiled with LLVM C11 support in Xcode. As such the following variant is necessary for the linker to not complain. {{{ variant c11 description { Build with C11 support. } conflicts universal gcc44 gcc45 gcc46 gcc47 { configure.cxxflags -stdlib=libc++ } }}} Given that LLVM is the default compiler now, this should perhaps even be a default variant.... /Lasse -- Comment: When you say "LLVM is the default compiler now", that's not true for all versions of Xcode that MacPorts supports (Xcode 2.4.1 and up, mostly). Why does this new variant need to conflict with universal? We like being able to build universal, so I would prefer if the default set of variants did not prevent it. Shouldn't you be appending to the cxxflags rather than overwriting them? -- Ticket URL: <https://trac.macports.org/ticket/38389#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X