summaryrefslogtreecommitdiffstats
path: root/fortran/test/Makefile.in
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r23305] HDFFV-8257: szip still used even if headers are not found. ↵Allen Byrne2013-02-181-1/+1
| | | | | | Change configure to test the result of the CHECK HEADERS call before checking for the library. Tested: local linux, h5committest
* [svn-r23293] Fix for HDFFV-8268: Fortran wrapper for H5Fget_file_image function.Scot Breitenfeld2013-02-181-3/+4
| | | | Tested: (jam, gnu,intel compilers)
* [svn-r22908] Reverted changes in revision 22819Larry Knox2012-10-161-2/+0
| | | | Tested with h5committest on jam, koala and ostrich.
* [svn-r22827] HDFFV-8007: Add missing H5O Fortran functions.Scot Breitenfeld2012-09-271-2/+4
| | | | | Tested: jam(gnu,intel)
* [svn-r22826] Fix for: HDFFV-7903 Fortran problem writing control character ↵Scot Breitenfeld2012-09-271-0/+2
| | | | | | to a dataset reconfigured
* [svn-r22825] Fix for: HDFFV-7903 Fortran problem writing control character ↵Scot Breitenfeld2012-09-271-2/+0
| | | | | | to a dataset Tested: (jam, gfortran)
* [svn-r22819] Added H5BLD_STATIC and HDF5_USE_SHLIB to configure.ac so that ↵Larry Knox2012-09-271-0/+2
| | | | | | if configured with --disable-static the default for HDF5_USE_SHLIB in the compile scripts will be changed to yes. This is a fix for HDFFV-8141, where the compile scripts try to link to non-existant static hdf5 libraries. Tested on jam,koala,ostrich(h5committest) and other THG machines.
* [svn-r22709] HDFFV-8129: reconfigured on jam, Remove overloading of ↵Allen Byrne2012-08-231-15/+16
| | | | | | autotools TESTS var, rename configure.in to configure.ac, convert test scripts from hard *.sh to configure managed *sh.in files. Tested: h5committest
* [svn-r22706] Updated autotools: autoconf 2.69, automake 1.12.3, m4 1.4.16, ↵Larry Knox2012-08-221-124/+148
| | | | | | libtool 2.4.2 Tested THG machines.
* [svn-r22510] Enabled the compilation of tH5E_F03.f90Scot Breitenfeld2012-07-031-7/+3
|
* [svn-r22504] Maintenance: Elena Pourmal2012-06-291-3/+7
| | | | | | | | See HELPDESK-643 issue in JIRA. NAG Fortran compiler doesn't like the current tH5E_F03.f90 file that has only comments and no executable statements. Removed tH5E_F03.f90 from the list of modules to build. Tested on jam with Intel compiler using --enable-fortran2003 flag.
* [svn-r21248] Mereged the F2003 branch into the trunk.Scot Breitenfeld2011-08-181-7/+38
| | | | | | | | | Items merged: fortran directory, src/libhdf5.settings.in configure.in configure MANIFEST Tested: (all platforms used by daily tests, both with --enable-fortran and --enable-fortran2003)
* [svn-r20504] Purpose:Mike McGreevy2011-04-141-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | General shared library improvements for CYGWIN / AIX Description: Shared libraries are disabled on both CYGWIN and AIX due to inability to build them correctly. Part of the problem in both of these situations is the lack of the libtool flag -no-undefined, which tells libtool that all needed symbols are defined at link time (a requirement on these systems) and that it's okay to build shared libraries. Another problem are lack of dependencies between wrapper libraries and core C HDF5 library. This patch addresses both of these by fixing configure to add in -no-undefined flag for libtool during linking and adds automake dependencies in the Makefile.am files. After testing, both CYGWIN and AIX now generate shared libraries, but there are still some test failures in each. (cache_api, dt_arith, and testerror.sh on CYGWIN, and fortran tests on AIX). Even though the shared libraries are not quite perfect, this is a general improvement to what we had before, so I'm applying the patch anyways. Note that default behavior of shared libraries on these systems being disabled has NOT been changed and requires the use of the --enable-unsupported to attempt to build them. We will need to address the test failures in each architecture prior to formally supporting shared libraries on each. Tested: h5committested & CYGWIN tested (on bangan) (AIX tested by Albert on bp-login2)
* [svn-r20502] Purpose:Mike McGreevy2011-04-141-25/+83
| | | | | | | | | | | | | | | | | | | | | | | | Add "silent make" mode configure option. Description: Automake 1.11 has a new option available that allows for a silent make mode. This functionality needs to be explicitly enabled in configure.in via the use of the automake macro AM_SILENT_RULES, which is what this commit is adding. This introduces a new configure option: --{en|dis}able-silent-rules This option is on by default, and simplies compile and link line outputs when building the library. Disabling this option will print full "verbose" output (i.e., full compile and linking lines for each target). Tested: This was tested on jam & h5committested
* [svn-r20475] Purpose:Mike McGreevy2011-04-111-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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-r19839] Updated to libtool v 2.4, autoconf 2.68 and m4-1.4.15.Larry Knox2010-11-231-0/+3
| | | | Tested with h5committest on amani, heiwa, and jam.
* [svn-r19506] Bring changes from revisions 19408, 19421, and 19442 from ↵Larry Knox2010-10-041-5/+15
| | | | | | branches/hdf5_1_8 to trunk. These revisions reorganize the compile scripts using h5cc.in, h5fc.in, and h5c++.in, add checks for installed examples to the scripts that run them after installation, and add DESTDIR for install as needed for RPMs. Tested on amani, heiwa and jam by h5committest and with CYGWIN.
* [svn-r19366] Updated autoconf to version 2.6.7, libtool to version 2.2.10, ↵Larry Knox2010-09-101-1/+1
| | | | | | and m4 to version 1.4.14. Also added m4 directory for m4 macros according to autoconf suggestion. Tested with h5committest on amani, jam, and heiwa, and on linew.
* [svn-r19059] Brought changes from hdf5_1_8 to add version information for ↵Larry Knox2010-07-091-0/+2
| | | | | | 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-r18709] Purpose:Mike McGreevy2010-05-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Improve configure's large-file support control. Description: Modified configure to now attempt to add defines necessary for supporting largefiles on all systems, instead of solely on linux. This is in response to user requests to enable largefile support on Solaris by default, as well as to give extra control on AIX (instead of just jamming the necessary flag into the config files). The old --enable-linux-lfs flag has been removed in favor of the --enable-largefile flag (enabled by default), which can be used on all platforms. On systems where large files cannot be supported in this manner, configure will report as such. Tested: h5committest AIX (NCSA's blue_print machine) duty, liberty, and linew.
* [svn-r18579] Purpose:Mike McGreevy2010-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Autotool Upgrade / Libtool Bug Fix Description: Updated autotools referenced in bin/reconfigure as follows: Autoconf 2.64 --> Autoconf 2.65 Automake 1.11 --> Automake 1.11.1 Libtool 2.2.6a --> Libtool 2.2.6b-mcg The referenced libtool version is a custom version of 2.2.6b. It has been tweaked to fix a bug in libtool that occurs when using PGI 10.0 compilers. A check incorrectly categorizes the C++ compiler as version 1.0 instead of 10.0, and the link line is subsequently set up incorrectly and fails to compile. A patch has been made available and will be included in the next release of libtool, but in the meantime I've applied the patch to a custom installation as indicated above. This bin/reconfigure now references the custom installation, and the resulting configure script will correctly categorize the PGI 10.0 C++ compiler. Ran bin/reconfigure to regenerate configure and makefiles. Tested: jam and amani with PGI 10.0 compilers. h5committest
* [svn-r18107] bug 1673:Albert Cheng2010-01-121-4/+4
| | | | | | | | | | | | | | The mixed use of RUNTEST (original) and RUNTESTS (new) caused confusion. E.g., the timings in test/ was still using the old $RUNTEST. It made more sense to use $RUNTEST which is used by the dejagnu feature of automake. So, I changed all $RUNTEST or $RUNTESTS to $RUNEXEC. config/commence.am & config/conclude.am are the two files that got changes. Also fixed an error in test/Makefile.am. The rest are changed by bin/reconfigure. Tested: h5committested.
* [svn-r17616] Purpose:Mike McGreevy2009-10-081-15/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-r17345] Purpose:Mike McGreevy2009-08-121-66/+100
| | | | | | | | | | | | | | | | | | | | | | | | Updating autotools Description: Installed new autotools and used them to reconfigure HDF5. - Automake upgraded to 1.11 - Autoconf upgraded to 2.64 - bin/reconfigure script edited to use new versions (on jam), and run to generate new configure script and Makefile.in's. - configure.in script edited to add "_cv_" to all AC_CACHE_VAL strings (in order to comply with new autoconf standard). Tested: Tested on machines jam, smirom, liberty, linew. Tested w/ features c++, fortran, parallel. Tested w/ compilers gcc, pgcc, icc. Further testing via Daily Tests should catch any other outliers. Upon passing DT's, I'll propogate the new tools into 1.8, hdf4, et cetera.
* [svn-r16792] Description:Mike McGreevy2009-04-201-4/+4
| | | | | | | | | | | | - Updated bin/reconfigure to use latest version of automake (1.10.2). Re-generated Makefile.in's by running bin/reconfigure. - Added libtool version numbers to c++, fortran, hl, hl c++, and hl fortran libraries. Tested: jam, liberty, smirom
* [svn-r16561] Purpose:Mike McGreevy2009-03-101-3/+3
| | | | | | | | | | | | | | | | | | 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-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a ↵Pedro Vicente Nunes2009-02-261-0/+1
| | | | | | | big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output) the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other tested: h5committest
* [svn-r15942] Purpose: Bug Fixes and Libtool UpgradeMike McGreevy2008-10-241-6/+6
| | | | | | | | | | | | | | | | | | Description: - Remove need to set LD_LIBRARY_PATH when using shared szip library. - Libtool 2.2.6a is now used to generate libraries. - 'make check install' dependency bug is fixed, and should no longer break the build. - removed hard coding of shell in config/commence.am, as this causes problems on Solaris with the new version of libtool. - RELEASE.txt with appropriate changes. Tested: - kagiso, smirom, linew (merged from 1.8, pretty quick tests)
* [svn-r15074] Maintenance: This check-in should fix daily tests failures:Elena Pourmal2008-05-271-53/+16
| | | | | | | | Uninstall target had non-existant file to remove; error_handler module triggered a race condition for parallel make with Intel and PGI compilers, therefore we removed the module and created a subroutine instead. Platforms tested: kagiso with GNU, Intel and PGI compilers.
* [svn-r15070] Description:Scot Breitenfeld2008-05-231-2/+2
| | | | fixed typo (minor fix)
* [svn-r15069] Purpose:Scot Breitenfeld2008-05-231-16/+44
| | | | | | | | Added code to remove module files when make clean Description: The module files were not being removed when make clean and caused compiling errors. fixed.
* [svn-r15067] Maintenance: Daily tests failed on several platforms due to the ↵Elena Pourmal2008-05-221-4/+4
| | | | | | | broken dependencies when srcdir and parallel make are used; fixed (I hope) Platforms tested: kagiso with srcdir and parallel make; pgcc and pgf90 -i8 compilers
* [svn-r15054] Purpose:Scot Breitenfeld2008-05-211-0/+9
| | | | | | | | | | | | Made reporting of the test status global by handling the output via a module. Cleaned-up output to the terminal. Description: Put writing the test status as a call to a subroutine instead of on a per account basis. Added the dependency of compiling in the correct order in the Makefiles for use of the Module.
* [svn-r15036] Bug fix.Albert Cheng2008-05-191-8/+9
| | | | | | | | | | | | | | | | | | | Description: The fortran Makefile.am used HDF_FORTRAN to indicate it is part of the Fortran API source so that conclude.am will give fortran api prefix in the test output. The symbox HDF_FORTRAN is also used in configure for a different purpose (indicated --enable-fortran). They conflicted. Similar problem for the symbol HDF_CXX. Solution: Changed all the involved Makefile.am to use "FORTRAN_API" instead. It is a more appropriate name. Same for CXX_API. Along the way, discovered that the Makefile.am of hl/fortran/test and hl/cxx/test did not have those symbols at all. Added them in. Platform tested: Kagiso only. It is a trivia change.
* [svn-r15007] Purpose: configure cleanupMike McGreevy2008-05-151-1/+0
| | | | | | | Description: cleaning up configure related to removal of --disable-hsizet flag, which we no longer support. Tested: kagiso
* [svn-r15003] Purpose:Albert Cheng2008-05-151-4/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improvement. Description: src/libhdf5.settings was the initial configure summary and is installed. Then configure is changed to dump a summary of the configure settings to the output and also append it to src/libhdf5.settings. That created two different output formats and duplicated information. This is the initial attempt to clean up this confusion and unify the output format. It is decided to use the src/libhdf5.settings template as the unified means. This requires more macros symbols be defined. The following symbols are all related to generating the src/libhdf5.settings file. AC_SUBST(EXTERNAL_FILTERS) AC_SUBST(MPE) MPE=no AC_SUBST(STATIC_EXEC) STATIC_EXEC=no AC_SUBST(HDF_FORTRAN) HDF_FORTRAN=no AC_SUBST(FC) HDF_FORTRAN=no AC_SUBST(HDF_CXX) HDF_CXX=no AC_SUBST(CXX) HDF_CXX=no AC_SUBST(HDF5_HL) HDF5_HL=yes AC_SUBST(GPFS) GPFS=no AC_SUBST(LINUX_LFS) LINUX_LFS=no AC_SUBST(INSTRUMENT) INSTRUMENT=no AC_SUBST(CODESTACK) CODESTACK=no AC_SUBST(HAVE_DMALLOC) HAVE_DMALLOC=no AC_SUBST(DIRECT_VFD) DIRECT_VFD=no AC_SUBST(THREADSAFE) THREADSAFE=no AC_SUBST(STATIC_SHARED) AC_SUBST(enable_shared) AC_SUBST(enable_static) AC_SUBST(UNAME_INFO) UNAME_INFO=`uname -a` The src/libhdf5.settings.in has CONDITIONAL's added to it too. The untrue conditions turned into a "#" and these lines are cleaned by the post processing script. Platform tested: h5committest on kagiso, smirom and linew.
* [svn-r14963] Removed dependency on unused routines for the fortranlib_test_1_8Scot Breitenfeld2008-05-091-7/+3
| | | | test program.
* [svn-r14933] Purpose: Updating HDF5 to use automake 1.10.1 and libtool 2.2.2Mike McGreevy2008-05-051-14/+18
| | | | | | | | | | | | | | | | | | Description: Applying update to autotools that was applied to 1.8 a couple of weeks ago to the trunk. Updated bin/reconfigure script to reflect the new versions of libtool and automake in the /home1/packages/ directory. Rearranged configure.in script. When using libtool 2.2.2, the libtool script doesn't generate until later in the configuration process, so I had to move a test that parsed through the libtool script to a point after where it was actually being generated. Ran libtoolize on the project, and ran bin/reconfigure to regenerate configure and Makefile.in's throughout. Tested: kagiso, smirom, linew (h5committest)
* [svn-r14923] Maintenance: This check-in merges changes from the fortran_1_8 ↵Elena Pourmal2008-05-031-36/+27
| | | | | | | branch back into the trunk (up to revision 14921) Platforms tested: kagiso with g95 and Intel compilers; more testing will be done after checking in a fresh copy from the trunk. New code itself was tested with all Fortran compilers available at THG
* [svn-r14903] Undoing change committed in r14902.Scot Breitenfeld2008-04-301-27/+36
|
* [svn-r14902] Merged fortran_1_8 branch changes r14505:14901 into the trunk. ↵Scot Breitenfeld2008-04-301-36/+27
| | | | New fortran wrappers added.
* [svn-r14402] Description:Quincey Koziol2008-01-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add work-around to allow reading files that were produced with a buggy earlier version of the library, which could create objects with the wrong object header message count. There is now a configure flag "--enable-strict-format-checks" which triggers a failure on reading a file with this sort of corruption (when enabled) and allows the object to be read (when disabled). The default value for the "strict-format-checks" flag is yes when the "debug" flag is enabled and no when the "debug" flag is disabled. Note that if strict format checks are disabled (allowing objects with this particular kind of corruption to be read) and the file is opened with write access, the library will re-write the object header for the corrupt object with the correct # of object header messages. This closes bugzilla bug #1010. Tested on: FreeBSD/32 6.2 (duty) in debug mode FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe, in debug mode Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN, in production mode Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN, in production mode Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN, w/szip filter, in production mode Mac OS X/32 10.4.10 (amazon) in debug mode Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
* [svn-r13972] Description:Quincey Koziol2007-07-131-0/+1
| | | | | | | | | Add --with-default-api-version configure flag. Tested on: Mac OS X/32 10.4.10 (amazon) FreeBSD/32 6.2 (duty) Linux/32 2.6 (kagiso)
* [svn-r13971] Description:Quincey Koziol2007-07-121-0/+1
| | | | | | | | | | | | | | Add --enable-deprecated-symbols configure option, to allow users to remove deprecated public API symbols at configure time. Add bin/make_vers script to bin/reconfigure actions. Run bin/reconfigure to regenerate autotool components. Tested on: Mac OS X/32 10.4.10 (amazon) FreeBSD/32 6.2 (duty) Linux/32 2.6 (kagiso)
* [svn-r13928] Purpose: 1) Moving H5_CXX_HAVE_OFFSETOF macro to ↵Mike McGreevy2007-06-291-3/+2
| | | | | | | | | | src/H5pubconf.h file. 2) Removing configuration of c++/src/H5cxx_pubconf.h file. Reasoning: the additional pubconf file caused compilation complications, this is cleaner. Tested: kagiso, smirom
* [svn-r13925] Purpose: intermediate checkin for offsetof fix for PGI compiler.Mike McGreevy2007-06-281-2/+3
| | | | | | | | | | Description: added new configuration to generate a pubconf file in the c++/src directory, H5cxx_pubconf.h. When C++ compiler recognizes 'offsetof', the macro H5_CXX_HAVE_OFFSETOF is defined in the new pubconf file. tested: kagiso, smirom
* [svn-r13846] Purpose: To remove changes from version #13839 (regarding ↵Mike McGreevy2007-06-081-1/+0
| | | | | | | | DEFAULT_VFD). Description: Changes made during this checkin need to be greatly modified, so I'm removing them now rather than leaving them in and fixing them later.
* [svn-r13839] Purpose: creation of a DEFAULT_VFD macro in the ↵Mike McGreevy2007-06-071-0/+1
| | | | | | | | | | | test/Makefile. Description: a new configure flag has been created that will now set a macro in the test/Makefile. The flag is with-default-vfd=. When set to a virtual file driver (e.g. "--with-default-vfd=sec2"), the macro DEFAULT_VFD will hold this value. Tested: kagiso, smirom, linew
* [svn-r13829] Some systems (only SGI Altix ProPack 4 discovered so far) ↵Raymond Lu2007-06-021-0/+1
| | | | | | | | | | | | doesn't return correct file size from MPI_File_get_size. Bypass this problem by replacing it with stat. Add an option --disable-mpi-size in configure to indicate this function doesn't work properly. Add a test in testpar/t_mpi.c, too. If it returns wrong file size, print out a warning. Tested on kagiso (parallel) because already tested the same change to v1.6 on several platforms (kagiso, cobalt, copper, and sol).
* [svn-r13815] Description:Quincey Koziol2007-05-291-0/+2
| | | | Regenerate configuration files after latest checkin
generated by cgit v0.12 at 2024-12-26 09:03:20 (GMT)