summaryrefslogtreecommitdiffstats
path: root/config
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r17902] SnapshotHDF Tester2009-11-171-1/+1
|
* [svn-r17742] Snapshot version 1.9 release 50HDF Tester2009-10-251-1/+1
|
* [svn-r17671] Removed these two options from the fortran flags:Albert Cheng2009-10-181-2/+2
| | | | | | | | | -qmoddir=. because -qmoddir defaults to current directory already. -static because it is not mentioned in "man xlf". Don't know it was a typo or just an obsoleted option. Removing both of them produced no ill or visible effects. Tested: Up of LLNL
* [svn-r17670] Snapshot version 1.9 release 49Larry Knox2009-10-181-1/+1
|
* [svn-r17663] Purpose:Mike McGreevy2009-10-161-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | configure cleanup Description 1. Removed check that disables shared libraries when pgcc is used. Apparently they previously did not work with libtool 1.5.14 and on mir, neither of which is in use anymore. Testing on jam and amani appear fine, so this check is unnecessary. 2. Removed check that disables shared C++ libraries when -xarch is used to enable 64 bit mode. We now use m64 flag to build 64 bit binaries, so we shouldn't explicitly disable shared C++ libraries if -xarch is discovered. 3. Removed old configure output summary section from configure.in, since we now use the libhdf5.settings file. 4. Updated powerpc-ibm-aix5.x config file to once again put c99 flag into H5_CFLAGS (and thus NOT get into h5cc), as decided in our dev meeting. Tested: h5committest full build with pgcc on jam / amani
* [svn-r17659] Changed the default fortran compilers from xlf and mpxlf_r toAlbert Cheng2009-10-161-4/+4
| | | | | | | | | | xlf90 and mpxlf90_r respectively. The fortran 90 compilers support free format source files. This allows the removal of -k so that the default compiler command is cleaner. Tested: AIX Up at LLNL. (Note: mpxlf90_r does not work but this could have been an undetected old problem.)
* [svn-r17654] Purpose:Mike McGreevy2009-10-157-24/+24
| | | | | | | | | | | | Configure cache-val cleanup Description: Corrected some misnamed cache values in configure / config files. Tested: h5committest
* [svn-r17644] Maintenance: Removed duplicated entry for socket library. It ↵Elena Pourmal2009-10-151-4/+3
| | | | | | | | | | was there for stream VFD. -lsocket is still used for linking, but it is added by libtool and not by us. Set up debug flags for Fortran. Platforms tested: linew 32 and 64-bit.
* [svn-r17643] Purpose:Mike McGreevy2009-10-141-2/+3
| | | | | | | | | | | | | | | | | | | Configure / Config File Fixes Description: 1. Made AM_CPPFLAGS assignments in configure a bit safer. (i.e., check to ensure include paths exist before adding them to AM_CPPFLAGS). 2. Change AIX config file to add -D_LARGE_FILES into AM_CXXFLAGS instead of H5_CXXFLAGS (same with *_CFLAGS). This will propagate it into h5c++, where it is needed to compile correctly. 3. Added missing line containing AM_CFLAGS to configure output summary. Tested: h5committest, and uP (AIX machine, via Albert).
* [svn-r17639] Purpose:Mike McGreevy2009-10-131-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | Configure Fix Description: uP (AIX Machine) was failing because configure needs to see -k flag in FCFLAGS for some checks to behave as intended. Since the config files were switched to passing all flags into H5_FCCFLAGS, this broke this behavior. To allow configure to see this again, FCFLAGS and all other user flags are saved before doing anything, and restored at the end of configure, so if needed we can set these values in configure and/or the config/ files without (permanently) overriding or changing anything a user sets. Also modified the powerpc-ibm-aix5.x config file to once again put -k into FCFLAGS in addition to H5_FCFLAGS (the former of which will be restored after configure completes the checks). Tested: h5committest (jam and amani finished, linew still running, though I wanted to get this in for daily tests since it needs to be run on uP for final verification).
* [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-r17628] Snapshot version 1.9 release 48Larry Knox2009-10-111-1/+1
|
* [svn-r17616] Purpose:Mike McGreevy2009-10-0829-1611/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-r17606] Code Cleanup:Albert Cheng2009-10-071-180/+0
| | | | | | | | TFLOPS machine has retired long ago. Removed all code specific for its support. Test: h5committested.
* [svn-r17589] Snapshot version 1.9 release 47Larry Knox2009-10-041-1/+1
|
* [svn-r17538] Snapshot version 1.9 release 46Larry Knox2009-09-271-1/+1
|
* [svn-r17446] Snapshot version 1.9 release 45Larry Knox2009-09-031-1/+1
|
* [svn-r17343] Snapshot version 1.9 release 44Larry Knox2009-08-121-1/+1
|
* [svn-r17248] Bug fix (1301 & 1468)Albert Cheng2009-07-281-2/+4
| | | | | | | | | | | | | | PathScale was mistaken as the Gcc compiler such that gcc flags were added to it but PathScale did not honor many of them. (e.g. -Wvariadic-macros, -Wold-style-definition, -Winit-self, -Wvariadic-macros, -Wmissing-include-dirs, -Winit-self, -Wc++-compat) Solution: Added a pre-condition to detect pathScale compiler before Gcc is accepted. Tested: Sandia Glory where PathScale compiler is available.
* [svn-r17196] Changed default Gnu fortran compiler from g95 to gfortran sinceAlbert Cheng2009-07-191-2/+2
| | | | | | | | | gfortran is more likely installed with gcc now. Tested: jam and amani which covers both linux and linux64. No h5committest because this is gnu compiler specific, usually applicable to Linux.
* [svn-r17159] Snapshot version 1.9 release 43Larry Knox2009-07-061-1/+1
|
* [svn-r17135] Snapshot version 1.9 release 42Larry Knox2009-07-011-1/+1
|
* [svn-r17047] Snapshot version 1.9 release 41Larry Knox2009-06-141-1/+1
|
* [svn-r17012] Snapshot version 1.9 release 40Larry Knox2009-06-071-1/+1
|
* [svn-r16995] Snapshot version 1.9 release 39Larry Knox2009-06-011-1/+1
|
* [svn-r16845] Description:Quincey Koziol2009-04-231-2/+59
| | | | | | | Updated with new warning flags from gcc 4.4 Tested: FreeBSD/64 6.3 (liberty) w/gcc 4.4.0
* [svn-r16789] Bug Fix (Bug 1398):Albert Cheng2009-04-201-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | | For gcc v4.3 and v4.4, with production mode, if -O3 is used, H5Tinit.c would fail to compile. Actually bad H5Tinit.c is produced. If -O (same as -O1) is used, H5Tinit.c compiled okay but test/dt_arith would fail with: Testing hard normalized long double -> signed char conversions time: comm and terminated abnormally When -O0 (no optimizatio) is used, H5Tinit.c compilete okay and all tests passed. Solution: Changed the config/gnu-flags to use -O0 for gcc v4.3 and 4.4 for production flags for now so that build and tests would work. Still need to investigate if the error is due to Gcc optimization bug or our code errors. Tested: In liberty with gcc43 and gcc44. Also, tested in jam and smirom with older versions of gcc. There are no gcc 43 or 44 compilers installed in other THG machines that I know.
* [svn-r16738] Snapshot version 1.9 release 38Larry Knox2009-04-111-1/+1
|
* [svn-r16704] Snapshot version 1.9 release 37Larry Knox2009-04-081-1/+1
|
* [svn-r16650] Snapshot version 1.9 release 36Larry Knox2009-04-011-1/+1
|
* [svn-r16579] Snapshot version 1.9 release 35Larry Knox2009-03-151-1/+1
|
* [svn-r16561] Purpose:Mike McGreevy2009-03-101-1/+0
| | | | | | | | | | | | | | | | | | Bug Fix Description: Fixing BZ #1381. The --includedir=DIR configure option, which is used to specify the installation location of C header files, did not work correctly as the path was hard-coded in config/commence.am. I'm presuming this is because an older version of automake didn't know where to put c header files. In any case, removing this line now defaults the includedir to the same directory that it is currently hard-coded to, and also fixes the configure flag to allow customization of this value. Tested: jam, liberty
* [svn-r16553] Snapshot version 1.9 release 34Larry Knox2009-03-081-1/+1
|
* [svn-r16525] Snapshot version 1.9 release 33HDF Tester2009-03-011-1/+1
|
* [svn-r16506] Snapshot version 1.9 release 32HDF Tester2009-02-221-1/+1
|
* [svn-r16492] revert gcc PROD_CFLAGS to "-O", which was incorrectly changed ↵Allen Byrne2009-02-191-1/+1
| | | | by rev 16489.
* [svn-r16489] Fixed bug #1459 by eliminating the macro long_long and ↵Allen Byrne2009-02-181-1/+1
| | | | | | | | | | | replacing all instances with long long. Tested: h5comittest fedora 10 x64 Vista 32, VS2005, IVF101 XP32, Cygwin
* [svn-r16484] Snapshot version 1.9 release 31HDF Tester2009-02-151-1/+1
|
* [svn-r16453] Snapshot version 1.9 release 30HDF Tester2009-02-081-1/+1
|
* [svn-r16397] Snapshot version 1.9 release 29HDF Tester2009-02-011-1/+1
|
* [svn-r16344] Snapshot version 1.9 release 28HDF Tester2009-01-251-1/+1
|
* [svn-r16340] Description:Frank Baker2009-01-222-2/+2
| | | | | | Changed 'THG' to 'The HDF Group' in various HDF5 source files, most of which are <subdirectory>/COPYING. -- Closes Bugzilla entry 1403.
* [svn-r16329] Snapshot version 1.9 release 27HDF Tester2009-01-181-1/+1
|
* [svn-r16220] Snapshot version 1.9 release 26HDF Tester2008-12-281-1/+1
|
* [svn-r16138] Snapshot version 1.9 release 25HDF Tester2008-11-301-1/+1
|
* [svn-r16121] Snapshot version 1.9 release 24HDF Tester2008-11-231-1/+1
|
* [svn-r16078] Snapshot version 1.9 release 23HDF Tester2008-11-161-1/+1
|
* [svn-r16044] Snapshot version 1.9 release 22HDF Tester2008-11-091-1/+1
|
* [svn-r16018] Snapshot version 1.9 release 21HDF Tester2008-11-021-1/+1
|
* [svn-r15953] Snapshot version 1.9 release 20HDF Tester2008-10-261-1/+1
|
generated by cgit v0.12 at 2024-11-01 19:42:39 (GMT)