summaryrefslogtreecommitdiffstats
path: root/configure
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r11449] Purpose:James Laird2005-09-211-1/+1
| | | | | | | | | | | | Bug fix Description: Fixed typo in configure.in. Platforms tested: SX6, mir Misc. update:
* [svn-r11439] Purpose:James Laird2005-09-191-3/+3
| | | | | | | | | | | | | | | | | | | | Bug fix Description: Using the -xarch=v9 flag to specify 64-bit compilation breaks C++ shared libraries. Disable shared C++ libraries if this flag is used. Solution: Instead of trying to disable compilers which recognize the -xarch flag, grep for it in CXX, CXXFLAGS, etc. Platforms tested: modi4, shanti, sleipnir Misc. update: Update to RELEASE and build instructions will be forthcoming once shared Fortran/C++ libraries are regularly passing the Daily Tests.
* [svn-r11421] Purpose:James Laird2005-09-161-32/+41
| | | | | | | | | | | | | | | Feature Description: Added H5_CFLAGS, etc. to 1.7 branch. Now compilation flags can be put in H5_*FLAGS and they'll be used when building hdf5 but not in h5cc. Platforms tested: mir, sleipnir, modi4 Misc. update:
* [svn-r11420] Purpose:James Laird2005-09-161-29/+65
| | | | | | | | | | | | | | | | | Bug fix Description: Disabled C++ shared libraries for Sun Workshop compiler. Solution: This bug only seems to happen when using the -xarch=v9 flag to compile in 64-bit mode, but disabling shared libraries entirely for this compiler is an easier fix (I don't know how to detect 64 bit mode from the command line). The framework for disabling shared libraries for other C++ compilers is in place. Platforms tested: sol, mir, sleipnir, modi4
* [svn-r11418] Purpose:James Laird2005-09-151-35/+83
| | | | | | | | | | | | | | | | Bug fix/feature Description: Disabled shared libraries for a number of Fortran compilers that don't support them. This allows other compilers to support shared Fortran libraries. Solution: Added a conditional, SHARED_FORTRAN_CONDITIONAL, which is true if Fortran supports shared libraries. It is set in configure.in. Platforms tested: mir, sleipnir, colonelk, heping
* [svn-r11411] Purpose:James Laird2005-09-131-43/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug fix Description: Building with --disable-static seems to have been broken on several platforms. Fixed this. Configure will now disable shared libraries automatically when using pgf90 or when building on Cygwin. Solution: To avoid errors when using shared libraries with pgf90 (which I had not realized were compiler-specific), I had manually set convenience libraries to use the -static linking flag. Apparently, this is not necessary, and caused these libraries to be created as empty archives when --disable-static was used. Also, some libraries were including other libraries, which was not necessary. I also fixed code in configure.in to correctly detect whether shared or static libraries are enabled, and moved code that disables shared libraries to before libtool is created (rather than editing libtool after the fact). Despite repeated warnings that only one shared library can be linked at a time, I have yet to have shared libraries break the linking of tests on any system. We'll see if the Daily Tests turn up anything. Platforms tested: mir (fortran, C++), sleipnir (C++), modi4 (fortran, C++, parallel), sol (fortran, C++), cygwin
* [svn-r11353] Purpose:James Laird2005-09-061-2/+13
| | | | | | | | | | | | | | | | | | Bug fix Description: Configure should now throw an error when C++ or threadsafe is enabled and a parallel compiler is being used. Platforms tested: sleipnir and modi4 Tested --enable-cxx --enable-parallel --disable-cxx --enable-cxx --disable-parallel cases in particular. Misc. update:
* [svn-r11350] Purpose:Albert Cheng2005-09-061-2/+2
| | | | | | | | | | | | | | | | | | Bug fix. Description: The incompatibility of enable-parallel and enable-cxx was not correctly coded. It would complained even for the case of ./configure --enable-cxx --disable-parallel. Solution: Changed it to use "$enable_XYZ" = "yes". Fixed the same for the enable-threadsafe checking too. Platforms tested: tested in heping. Misc. update:
* [svn-r11344] Purpose:Quincey Koziol2005-09-031-6/+0
| | | | | | | | | | | Bug fix Description: Allow threadsafe & C++ to be enabled together - its working fine on sleipnir. Platforms tested: FreeBSD 4.11 (sleipnir)
* [svn-r11336] Purpose:James Laird2005-09-011-2/+2
| | | | | | | | | | Bug fix Description: A typo made configure throw an error if only C++ was enabled. Fixed. Platforms tested: mir
* [svn-r11335] Purpose:James Laird2005-09-011-3/+7
| | | | | | | | | | | | | | | Bug fix Description: configure used 'uname -o' to detect Cygwin. This command is fine on Cygwin, but causes errors on some other platforms (sol). Fixed this. Solution: Used 'uname' with no -o option to identify Cygwin. Platforms tested: mir, cygwin (on finrod)
* [svn-r11334] Purpose:James Laird2005-09-011-0/+26
| | | | | | | | | | | | | | | | | | | | Feature: checking configure flags (bug #90) Description: Some configure flags don't work together. Configure now exits with a sensible error message if one of these combinations is specified. Solution: The following flags will throw errors: --enable-cxx and --enable-parallel --enable-cxx and --enable-threadsafe --enable-threadsafe and --enable-parallel --enable-fphdf5 and --enable-fortran Platforms tested: mir, modi4, heping Misc. update:
* [svn-r11333] Purpose: Change configure's default.Raymond Lu2005-09-011-2/+2
| | | | | | | | | Description: Changed configure's default disable-dconv-exception and disable-dconv-accuracy back to enable-dconv-exception and enable-dconv-accuracy. The test has been finished. Platforms tested: fuss - tested before.
* [svn-r11320] Purpose: TestRaymond Lu2005-08-311-1/+1
| | | | | | | | | Description: made --disable-dconv-accuracy default to let daily test check every systems. Will change it back to --enable-dconv-accuracy afterwards. Platforms tested: h5committest
* [svn-r11318] Purpose: TestRaymond Lu2005-08-301-1/+1
| | | | | | | | | Description: made --disable-dconv-exception default for configuration to let daily test run on every system. The default was --enable-dconv-exception. Platforms tested: h5committest and fuss.
* [svn-r11315] Purpose: Minor change on feature.Raymond Lu2005-08-301-39/+40
| | | | | | | | | Description: Changed the configuration options --enable-exception and --enable-accuracy checked in yesterday to --enable-dconv-exception and --enable-dconv-accuracy to be more descriptive. Platforms tested: fuss - simple change.
* [svn-r11311] Purpose: New features.Raymond Lu2005-08-291-192/+268
| | | | | | | | | | | | | | | | | | | | Description: Added 2 new configure options, --enable-exception and --enable-accuracy. --enable-exception lets the library check whether user's exception handling functions are present during compiler data conversions and use them if they are. When it's disabled, this step is skipped to improve conversion speed. This step isn't implemented yet for soft conversions because there would be little gain in speed. --enable-accuracy guarantees data accuracy during data conversions. It means the library will choose compiler conversions only if the accurate data is secured. Otherwise, the library will go for the library's own conversions. If this option is disabled, the library uses compiler conversions in favor of their speed as long as they work even if data can be incorrect. Platforms tested: h5committest and fuss. Some systems may fail after this checkin.
* [svn-r11252] Purpose:Albert Cheng2005-08-161-1/+1
| | | | | | | Fixed a typo--osf1 was spelled as osfl. Platforms tested: Tflops.
* [svn-r11222] Purpose:Albert Cheng2005-08-091-0/+110
| | | | | | | | feature Description: Add the test for tmpfile. If it does not exist, compile in our own version (which always returns NULL for now.)
* [svn-r11204] Snapshot version 1.7 release 50HDF Admin2005-08-071-10/+10
|
* [svn-r11148] Snapshot version 1.7 release 49HDF Admin2005-07-241-10/+10
|
* [svn-r11144] Purpose:Quincey Koziol2005-07-231-0/+19
| | | | | | | | | | | New port Description: Elena asked me to check in her NEC SX-6 work, so here it is! :-) Platforms tested: FreeBSD 4.11 (sleipnir) NEC SX-6 (by Elena)
* [svn-r11087] Purpose: Bug fix.Raymond Lu2005-07-191-0/+70
| | | | | | | | | | | | | | Description: When converting floating-point numbers to integers and the values of floating-point number are greater than the maximal value of integer, Cray X1 generates floating exception. Solution: Added a test in configure to detect Cray X1's exception. Set a flag to indicate the machine that can handle overflow converting all floating-point to all integer types. This flag should be set for all machines, except for Cray X1 where floating exception is generated when the floating-point value is greater than the maximal integer value. Platforms tested: Cray X1 and h5committest.
* [svn-r11085] Purpose:James Laird2005-07-191-15/+1
| | | | | | | | | | | | | | | Bug fix Description: Update Makefiles now that docs are no longer in main hdf5 tree. Solution: Changed root-level Makefile.am not to recurse into docs tree. Removed docs Makefiles from configure.in. Removed config/commence-doc.am, since it is no longer used. Platforms tested: mir (change to Makefiles only)
* [svn-r11083] Purpose:James Laird2005-07-181-2/+2
| | | | | | | | | | | | Bug fixes Description: A number of minor changes to Makefiles. Some files will now be cleaned properly, some comments are more informative, etc. Platforms tested: heping, mir, modi4
* [svn-r11081] Snapshot version 1.7 release 48HDF Admin2005-07-181-10/+10
|
* [svn-r11019] Purpose: Add detectionRaymond Lu2005-07-051-0/+4
| | | | | | | | | | | Description: pgcc version 6.0x have optimization (-O, -O2, or -O3) problem. It caused multi driver test to fail. The problem happened in a macro definition. Solution: Detect these versions and add option "-Mx,28,0x8" to the compiler to avoid the problem if optimization is enable. Platforms tested: mir and fuss - simple change.
* [svn-r10956] James Laird2005-06-201-31/+37
| | | | | | | | | | | | | | | | | | | Purpose: Configuration feature Description: Added 'alias' for host names in configure. Typing ./configure --host=tflops will now configure with tflops as a host. Previously, this required typing ./configure --host=i386-intel-osfl. Solution: Added a section in configure.in which will replace 'tflops' with 'i386-intel-osfl'. Platforms tested: sleipnir, mir, heping Misc. update:
* [svn-r10879] Purpose:MuQun Yang2005-06-081-1/+154
| | | | | | | | | | | | | | Removing configuration warnings on cygwin. Description: winsock.h cannot be compiled by cygwin and that generates configuration warnings. Remove checking winsock.h on cygwin. Solution: Platforms tested: Misc. update:
* [svn-r10847] Purpose: Bug fixRaymond Lu2005-06-021-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Description: See details from Bug #213. Family member file size wasn't saved anywhere in file. When family file is opened, the first member size determine the member size. Solution: This is the fourth step of checkin. A test suit is added for h5repart, including a program to generate the test files, a script file to run h5repart, and a program to verify repartitioned files can be opened by the library. There's a change from the first step of checkin. Family name template is no longer saved in the superblock because different pathname can make the name different. In the third step of checkin, h5repart has been modified. If h5repart is used to change the size of family member file, the new size(actual member size) is saved in the superblock. In the second step of checkin, multi driver is checked against the driver name saved in superblock. Wrong driver will result in a failure with an error message indicating multi driver should be used. This change includes split driver because it's a special case for multi driver. In the first step of checkin. Family member size and name template(unused at this stage) are saved in file superblock. When file is reopened,the size passed in thrin superblock. A different size will trigger a failure with an error message indicating the right size. Wrong driver to open family file will cause a failure, too. Platforms tested: h5committest and fuss. Misc. update: MANIFEST
* [svn-r10802] Purpose:James Laird2005-05-251-31/+32
| | | | | | | | | | | | | | | | Configuration feature Description: Formerly, bin/reconfigure needed to invoke Automake with the --foreign flag or it would fail. It turns out that there is a clever way to specify this flag inside configure.in so that it doesn't need to be explicitly invoked. This should make it easier for people not using machines connected to AFS (e.g., the netCDF folks) to invoke Automake on HDF5. Platforms tested: mir and heping
* [svn-r10797] Purpose: A featureRaymond Lu2005-05-251-6/+40
| | | | | | | | | | | Description: Cygwin compiler doesn't do rounding correctly when converting "unsigned long long" to "long double". Solution: Added test case to variable detection of "hdf5_cv_ullong_to_ldouble_precision_works". Platforms tested: sleipnir, fuss, and shanti - mainly to test configuration, don't need to run h5committest.
* [svn-r10773] Purpose:James Laird2005-05-201-1/+1
| | | | | | | | | | | | | Output tweak Description: In configure.in, users must link to zlib library, but configure then informs them that "deflate" filter is enabled. Changed output slightly to indicate that these are the same filter. Platforms tested: mir (very minor change)
* [svn-r10744] Snapshot version 1.7 release 47HDF Admin2005-05-151-10/+10
|
* [svn-r10730] Purpose:James Laird2005-05-051-0/+111
| | | | | | | | | | | | | | | | Portability feature Description: The random() and srandom() functions are not available on all machines. Set up the configure script to automatically detect them, rather than requiring their presence or absence to be hardcoded. Solution: Added AC_CHECK_FUNCS macro to configure.in and replaced #ifdef WIN32 conditionals with #ifdef H5_HAVE_RANDOM conditionals. Platforms tested: sleipnir, Windows
* [svn-r10700] Purpose:Quincey Koziol2005-04-291-0/+22
| | | | | | | | | | | | | | | Bug fix Description: Kent reminded me that switching the logic wasn't enough, we really needed to add the definition to the configure script. Solution: Do that. Platforms tested: FreeBSD 4.11 (sleipnir) Too minor to require h5committest
* [svn-r10657] Purpose:James Laird2005-04-251-2/+1
| | | | | | | | | | | | | | | | | | | | Configuration feature Description: Fortran integer types (not reals) are now automatically detected at build-time. Solution: Two helper programs are used, one to detect what types the Fortran compiler has access to, and one to generate header files for C and Fortran matching up types. Platforms tested: mir, copper, modi4, pommier (last week) Misc. update: MANIFEST updated, H5f90fortran_types.f90 removed from configure.in, since it is not longer generated by configure.
* [svn-r10632] Snapshot version 1.7 release 46HDF Admin2005-04-201-10/+10
|
* [svn-r10570] Purpose: MaintenanceElena Pourmal2005-04-071-1296/+32
| | | | | | | | | | | Description: Removed support for SRB driver Solution: Removed or modified appropriate files; ran reconfigure to regenerate Makefile.in and configure files. Platforms tested: heping and shanti Misc. update: ran bin/chkmanifest on heping
* [svn-r10534] Purpose:James Laird2005-04-041-52/+3711
| | | | | | | | | | | | | | | | | | | | Configuration feature Description: Different Fortran compilers mangle function names in different ways (upper case, lower case, adding underscores). To link between Fortran and C functions, we need to know what a given function's name is under a given compiler. Solution: Use autoconf's FC_WRAPPERS check to determine the Fortran naming scheme and define the FC_FUNC_ macro to name our functions (in H5f90proto.h). Removed references to our old FNAME macro, as well as flags that indicated whether function names were upper or lower case. Platforms tested: mir, pommier, modi4, copper, more
* [svn-r10475] Purpose:James Laird2005-03-291-1/+21
| | | | | | | | | | | | | | | | | Feature - conditional compilation Description: SRB file driver and tests are now compiled only when SRB is enabled (using --with-srb during configure). Solution: Added an automake conditional in configure.in, altered Makefiles.am in src and test directories to depend on that conditional. This should make a nice example for posterity to add conditionally compiled sources. Platforms tested: heping (only configure change)
* [svn-r10459] James Laird2005-03-281-1/+4
| | | | | | | | | | | | | | | | | Purpose: Added C++ wrapper for Packet Table API. Description: Added macro for high-level C++ library (LIBH5CPP_HL), which changes every Makefile.in. Added directories for high-level C++ library (though currently only Packet Table API is supported). Added both C++ source and tests. Platforms tested: sleipnir, mir, modi4 Misc. update:
* [svn-r10215] Purpose:James Laird2005-03-141-29/+33
| | | | | | | | | | | | | | | | | Configure feature Description: On some platforms with some compilers, automake's dependency tracking is silently disabled. This can be confusing for developers. Solution: Set configure to enable dependencies all the time unless the user explicitly disables them (using the configure flag --disable-dependency-tracking) or a site file overrides the default (as is the case on IRIX). Platforms tested: sleipnir, mir
* [svn-r10201] Purpose:MuQun Yang2005-03-111-0/+22
| | | | | | | | | | | | | | | | | | | | | IBM MPI-IO has a bug for MPI derived data type, which is used to support collective IO. In order to avoid this, we provide a way to turn off collective IO support for this kind of platform. Description: Using a new macro called H5_MPI_COMPLEX_DERIVED_DATATYPE_WORKS to turn off irregular hyperslab collective IO support at such platforms. Solution: Hard code such platforms under hdf5/config. So far only IBM AIX has been found to have such problems. Platforms tested: heping (Linux) and copper(Aix). Testing at tungsten now, however, it took almost an hour to build parallel HDF5 at tungsten, it is still building. Cannot wait. Have tested this feature at Tungsten a week ago. Misc. update:
* [svn-r10179] Purpose:James Laird2005-03-101-79/+100
| | | | | | | | | | | | | | | Automake update cleanup and minor changes Description: Removed macros in acsite.m4 that are no longer used. Switched to using autoconf's AC_LANG_PUSH(Fortran) instead of old AC_LANG_FORTRAN9X macro. Switched to using AC_LANG_PUSH() and AC_LANG_POP() (from old AC_LANG_X). Added ifort to list of Fortran compilers configure will look for. Added a note about automake change to Release Notes. Platforms tested: copper, modi4 (parallel and serial), eirene
* [svn-r10174] Purpose:James Laird2005-03-091-28/+28
| | | | | | | | | | | | | | | | | | | Bug fix Description: acsite.m4 contains macros to handle fortran compiler. Some of these macros are obsolete with automake 1.9.5, but some of them are still used. These macros need to refer to the fortran compiler as $FC, not $F9X. Solution: The version of acsite.m4 with this change didn't get checked in last time. Oops. Replaced all occurances of $F9X with $FC and $FFLAGS with $FCFLAGS in acsite.m4. Platforms tested: copper, modi4 (serial and parallel), kelgia, eirene. Some errors from btree code and ph5diff. No errors in fortran/test.
* [svn-r10171] Purpose:James Laird2005-03-091-30/+34
| | | | | | | | | | | | | | | | | | | Bug fix Description: The fortran compiler is named FC. If F9X environment variable is set, FC should hold the value in F9X. However, this was overwriting values written to FC by platform-specific config scripts. This caused copper to find the wrong fortran when building in parallel, and may have had other symptoms on other platforms. Solution: Assign $F9X to $FC at the beginning of configure, before platform-specific scripts are run. Do this assignment only if FC is empty. Platforms tested: copper, modi4 (parallel and serial w/c++), verbena. This change should only affect fortran build.
* [svn-r10160] Purpose:James Laird2005-03-071-74/+59
| | | | | | | | | | | Forgot to run reconfigure Description: Forgot to run bin/reconfigure after removing my debug output from configure.in. Shame on me! Platforms tested: mir
* [svn-r10158] Purpose:James Laird2005-03-071-263/+523
| | | | | | | | | | | | | | | | | | | | | | Automake version upgrade Description: Upgraded automake version from 1.6.2 to 1.9.5. Changed bin/reconfigure script to use automake 1.9.5. Changed configure.in and Makefiles to use new FCFLAGS and FC variables instead of FFLAGS and F9X. Automake and configure should now do the lion's share of the work supporting Fortran 9X; macros in acsite.m4 are now mostly unused (will be cleaned later). Altered how configure handles pmake; now root-level Makefile.in is processed by bin/reconfigure to have a .MAKEFLAGS target, since automake no longer allows us to define unused variables. Configure now always checks for C++ compiler even if it is not used, since automake thinks this is the Right Thing To Do and will break otherwise. Platforms tested: Sol, copper, heping, mir, sleipnir, eirene, pommier, kelgia, modi4.
* [svn-r10132] Purpose:James Laird2005-03-031-2/+4
| | | | | | | | | | | | | | | Bug fix Description: When C flags are passed in using $CC variable, this can confuse test commands in configure (for instance, CC='pgcc -tp k8-32'). Solution: Previous solution didn't entirely solve problem. Wrote a sed snippit to strip flags from $CC for purposes of test in configure. Platforms tested: mir (just a configure bug)
generated by cgit v0.12 at 2024-11-05 08:59:10 (GMT)