chapel: compiler, archs

[ryandesign (Ryan Carsten Schmidt)]

chapel does not ensure it's UsingTheRightCompiler nor does it respect build_arch or have a universal variant. r81358.

[tenomoto (Takeshi Enomoto)]

chapel builds out of the box since gnu is selected for darwin among the Makefiles provided by the developer. In revision 1, ${worksrcpath}/make/compiler/Makefile.gnu is edited to ensure UsingTheRightCompiler, to respect build_arch and support +universal.

Although not tried every possible combinations, I confirmed build_arch=i386, +universal and configure.compiler=macports-gcc-4.5 works on a x86_64 machine running Lion.

Committed in r81280.

[ryandesign (Ryan Carsten Schmidt)]

Now chapel does not install on Snow Leopard, or probably anything earlier either:

$ sudo port configure
--->  Fetching chapel
--->  Verifying checksum(s) for chapel
--->  Extracting chapel
--->  Configuring chapel
Error: chapel requires configure.compiler=*-gcc-*.
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>

[tenomoto (Takeshi Enomoto)]

Realized that *-gcc-* could be llvm-gcc and that the default compiler is gcc-4.x (not apple-gcc-4.x) before Lion. Modified to detect llvm or clang. r81304.

[ryandesign (Ryan Carsten Schmidt)]

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. ​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.

[tenomoto (Takeshi Enomoto)]

I thought the user has to specify configure.compiler=gcc-4.2 explicitly. I modified to simply force gcc-4.2. The build fails without warnings when configure.compiler=clang is specified, for example.

r81358