#30376: chapel: compiler, archs --------------------------------------+------------------------------------- Reporter: ryandesign@… | Owner: takeshi@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: Port: chapel | --------------------------------------+------------------------------------- Changes (by ryandesign@…): * status: closed => reopened * resolution: fixed => Comment: Now that will fail to build on Lion, won't it? I don't have Lion yet, but the default compiler there is llvm-gcc-4.2, and if I simulate the Lion experience by requesting that compiler on Snow Leopard, I get: {{{ $ sudo port configure configure.compiler=llvm-gcc-4.2 ---> Fetching chapel ---> Verifying checksum(s) for chapel ---> Extracting chapel ---> Configuring chapel Error: chapel does not work properly with llvm-gcc or clang. Error: Target org.macports.configure returned: Log for chapel is at: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_lang_chapel/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> }}} If you're wanting to force the use of gcc instead of llvm-gcc-4.2 or clang, then just do that. [http://lists.macosforge.org/pipermail/macports- dev/2011-July/015263.html This mailing list post] shows the block we're currently recommending for accomplishing that. But please report the clang and llvm-gcc problems to the developers of this software so they can resolve them. clang is the future on Mac OS X and software that doesn't work with it won't work on Macs in the future. -- Ticket URL: <https://trac.macports.org/ticket/30376#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS