summaryrefslogtreecommitdiffstats
path: root/config/apple
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r23441] HDFFV-8245: bug fix. Snow Leopard (darwin 10.X) does not have ↵Albert Cheng2013-03-251-3/+12
| | | | | | | | | clang++. Reversed it to use gcc/g++ as the default C and CXX compilers for Darwin 10.X systems. Tested: duck (darwin 11), wren (darwin 12) and fred (darwin 10).
* [svn-r23434] Improvement: DFFV-8245Albert Cheng2013-03-221-4/+35
| | | | | | | | | | | | | | Use Clang as the compiler for the Mac platform. Changed all Mac to use clang/clang++ as the default C and CXX compilers if not provided by the user. Still use gfortran as the default fortran compiler since Apple does not provide any fortran compiler. Tested: passed all three macs OS, snow leapord (fred), lion (duck) and mountain lion (wren). Also passed test using Apple gcc, Gnu gcc, Intel as the C compilers and all corresponding CXX compilers fits in. Did not run h5committest or other non-mac platform since this change affect Apple platforms only.
* [svn-r23235] Fix for:Scot Breitenfeld2013-02-081-6/+4
| | | | | | | HDFFV-7909 When building with g95 on Mac OS X 64-bit, the wrong options (gfortran) are used Tested: duck (gfortran, g95 (which is not supported))
* [svn-r22879] Bug Fix: HDFFV 8017Albert Cheng2012-10-101-0/+16
| | | | | | | | | | | | | | | dt_arith would fail in Lion and Mountain Lion system when GCC version 4.2.1 is used with --enable-production. Somehow the -O optimization will fail some of the hard conversion code. Solution: This is just a temporary patch by detecting if this is a Lion or Mountain Lion system using GCC 4.2.1, then just remove the any -O option from the PROD_CFLAGS. A better fix should be deviced later. Tested: Duck(lion) and Owl (mountain lion) tested with --enable-production. Also tested in Fred and Tejeda, both Snow Leopard systems to verify there is no undesired side effect.
* [svn-r20475] Purpose:Mike McGreevy2011-04-111-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Revise shared Fortran library disabling scenarios in configure - Improve configure output summary Description: Shared Fortran libraries are not supported on Mac, but were being disabled by configure in a way that also forced the C libraries to be static-only. This has been fixed, so now only shared Fortran is disabled while shared C can remain. This prompted two additional changes: 1. While working on the check that addresses whether or not shared Fortran libraries are allowed, removed old and no longer needed check(s) that disable shared Fortran libraries with HP, Intel 8, PGI, and Absoft compilers. (Essentially, Mac is the only situation in which Fortran shared are disabled by configure.) 2. Having two different states of libraries (i.e. shared C library with static-only Fortran library) was not apparent in the configure summary, which labeled all libraries as either shared and/or static. I've added lines to both the C++ and Fortran output sections to list shared/static-ness of these libraries specifically. Additionally, I've made sure that the new --enable-unsupported configure option correctly overrides configure if it tries to disable a shared library. Tested: jam, fred, & h5committest
* [svn-r19566] Maintenance: Added -O3 to be used with the C Intel v 11 ↵Elena Pourmal2010-10-081-0/+21
| | | | | | | | | compilers; set default to -O for all unknown versions of the C Intel compilers. Modified apple config file to display Intel compiler information. Updated RELEASE.txt notes accordingly. Platfroms tested: jam, amani and dubna (Mac 64-bit) with Intel C, Fortran and C++ compilers.
* [svn-r19059] Brought changes from hdf5_1_8 to add version information for ↵Larry Knox2010-07-091-0/+30
| | | | | | fortran and c++ compilers in libhdf5.settings file and configure output (r18836), to install examples as part of make install (r18680), and to provide scripts to compile and run the examples after they are installed (r18817). Tested with new/h5committest on amani, heiwa, and jam.
* [svn-r17636] Maintenance: Changed default fortran compiler for Mac Intel to ↵Elena Pourmal2009-10-131-46/+23
| | | | | | | | | | | gfortran Cleaned up the file to be inline with other config files that use multiple compilers. Platforms tested: My Mac pahra with gfortran, ifort and g95
* [svn-r17616] Purpose:Mike McGreevy2009-10-081-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CFLAGS overhaul Description: Modified the way configure handles CFLAGS. (note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS). 1. The configure process will now always preserve a user's CFLAGS environment variable setup. Any additional flags necessary for compilation added at configure time will be passed into the Makefiles as AM_CFLAGS, which is an automake construct to be used in addition to CFLAGS. This will allow a user to have the final say, as CFLAGS will always appear later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS during make will no longer completely erase all flags set by configure, since they're maintained in AM_CFLAGS. 2. Additionally, where possible, flags previously being assigned directly into CFLAGS (and thus propagating into h5cc) have now been redirected into H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into the h5cc wrapper script as well. *Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the Makefiles. Complete description of changes and build process will be included in a Configure Document that Elena and I are working on. 3. Removed unsupported config files. This includes: config/dec-osf* config/hpux11.00 config/irix5.x config/powerpc-ibm-aix4.x config/rs6000-ibm-aix5.x config/unicos* 4. Modified configure summary to display additional values. Specifically, appropriate AM_* variables are being shown, as well as H5_FCFLAGS and H5_CXXFLAGS, which were for some reason not already present. Tested: - H5committest - Tested on all THG / NCSA machines, using several combinations of the more prominent configure options (c++, fortran, szip, threadsafe, parallel, et cetera). (Thanks to Quincey for rysnc testing setup!) - With regards to new automated testing, anything *necessary* for compilation will be caught by the daily tests as it stands now. (i.e., if LDFLAGS is not properly set when szip is used, linking will fail). Additionally, with regards to which flags get into h5cc, if any *necessary* flags have been improperly removed, then daily tests should fail during make installcheck. Additional machine-specific desired behaviors and/or checks may have to be set up separately within the daily tests, so this is something to work on.
* [svn-r13934] Description:Quincey Koziol2007-07-031-0/+81
Rename Mac OS X compiler configuration file to more generic name, which should allow Intel Macs to configure better. Tested on: Mac OS X/32 10.4.10 (amazon)