Hello community, here is the log from the commit of package parallel-netcdf for openSUSE:Factory checked in at 2016-08-10 21:56:34 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/parallel-netcdf (Old) and /work/SRC/openSUSE:Factory/.parallel-netcdf.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "parallel-netcdf" Changes: -------- --- /work/SRC/openSUSE:Factory/parallel-netcdf/parallel-netcdf.changes 2015-08-03 17:22:27.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.parallel-netcdf.new/parallel-netcdf.changes 2016-08-10 21:56:36.000000000 +0200 @@ -1,0 +2,150 @@ +Sun Jul 17 16:14:30 UTC 2016 - [email protected] + +- Trim descriptions. + +------------------------------------------------------------------- +Thu Jul 14 14:58:10 UTC 2016 - [email protected] + +- Update to 1.7.0 + o New features + * Nonblocking requests now can be posted while the program is in the define + mode. This feature enables applications to add new variables and post the + nonblocking write requests without separating the codes by + ncmpi_enddef(). Note ncmpi_wait_all and ncmpi_wait must still be called + in the data mode. + * When using immutable write buffer in put APIs on a Little Endian machine, + the in-place byte swap operation performed internally in PnetCDF can + cause a fatal error (by trying to change the contents of an immutable + memory space). The solution of copying user's write request to a + temporary buffer and perform byte swap there conflicts with PnetCDF's + design principle of avoiding internal memory allocation as much as + possible. Since the size of immutable buffer in most cases is small, + PnetCDF now compromise the two by making a copy of write requests that is + less than 4KB. Users are warned that using immutable write buffer larger + than 4KB will still cause the fatal error in the PnetCDF default + configuration. The way to completely disable in-place byte swap is to + build PnetCDF with --disable-in-place-swap option at the configure time. + In this case, the internal memory allocation in PnetCDF will increase. + o Syntax changes + * In ncmpi_wait_all(), ncmpi_wait(), and ncmpi_cancel(), the API's third + argument, array of requests IDs, is changed to INOUT. Upon successful + completion or cancellation of individual nonblocking requests, the + corresponding request IDs are set to NC_REQ_NULL. + o New run-time environment variables + * PNETCDF_VERBOSE_DEBUG_MODE environment variable can be used to print the + location in the source code where the error code is originated, no matter + the error is intended or not. This run-time environment variable only + takes effect when PnetCDF is configure with debug mode, i.e. + --enable-debug is used at the configure command line. Set this variable + to 1 to enable. Set it to 0 or keep it unset disables this mode. Default + is 0, i.e. disabled. Users are warned that enabling this mode may result + in a lot of debugging messages printed in stderr. + o New example programs + * examples/C/nonblocking_write_in_def.c shows an example of posting + nonblocking write requests in the define mode. + * examples/C/req_all.c shows an example of using NC_REQ_ALL to flush all + pending nonblocking requests without providing the requests IDs. + o New test program + * test/cdf_format/dim_cdf12.c tests defining maximal dimension size for + CDF-1 and CDF-2 file formats + * test/testcases/test_erange.c tests if the error code NC_ERANGE can be + correctly returned for two cases 1) get a NC_UBYTE value of 255 from a + netCDF file to a memory buffer of type signed char and 2) put a value + of -1 of signed char to a NC_UBYTE variable in a netCDF file + * test/testcases/check_type.c tests if the error codes can be correctly + returned when conflicted in-memory and extenal data types are used. + * test/testcases/put_parameter.f tests the use of immutable write buffer + (e.g. a buffer declared as PARAMETER). Note the buffer size must be + smaller than 4KB. + * test/nonblocking/i_varn_indef.c tests posting nonblocking requests in + define mode. + * test/nonblocking/req_all.c tests the use of NC_REQ_ALL for flushing + all pending nonblocking requests without providing the requests IDs. + * test/last_large_var.c tests the special case when there is no record + variable, the last fixed-size variable can be larger than 2GiB in size + if its starting file offset is less than 2GiB. + * test/testcases/buftype_free.c and test/testcases/buftype_freef.f test + the bug in r2160. + * testcases/add_var.c checks the starting file offsets of newly added + variables from re-entering the define mode. + * testcases/attrf.f checks NF_ERANGE is returned instead of coredump. This + is particularly for NAG Fortran compiler that may report "Arithmetics + exception". + * testcases/check_striping.c checks if the file striping unit and factor + returned from MPI-IO hints are consistent among processes. + * test/nonblocking/column_wise.c checks if PnetCDF detects interleaved + fileviews from multiple nonblocking requests and correctly breaks and + reconstructs the fileviews so the combined fileview is monotonic + non-decreasing in file offsets. + o New optimization + * Filling variables at ncmpi_enddef() is now done by aggregating all write + requests into one MPI collective write call. In v 1.6.1, this is done by + filling one variable at a time. + o New utility program + * ncoffsets reports the file offset information, including the starting and + ending file offsets, of variables stored in a netCDF file. ncoffsets is + compiled with gcc if gcc is presented on the build system. Additional + command-line options are: (-v) reports only for a selected list of + variables in interest, (-s) prints the variable sizes, (-g) outputs the + file space gap size from the end of previous variable, (-x) reports + whether there is a gap between any two adjacent fixed-size variables. See + the man page for descriptions of all command-line options and examples. + o Semantics updates + * All nonblocking APIs now take a NULL pointer for the request ID argument, + meaning users do not wish to keep track of the request ID. If NULL + request IDs are used, NC_REQ_ALL should be used when calling + ncmpi_wait_all/ncmpi_wait to commit all the pending nonblocking requests. + This feature relinquishes users from the responsibility of tracking the + IDs of pending requests. + * Using NC_REQ_ALL as the 2nd argument "num" in ncmpi_wait_all/ncmpi_wait + APIs will flush all the pending nonblocking requests. In this case, the + 3rd and 4th arguments "array_of_requests" and "array_of_statuses" will be + ignored and thus these two arguments can be NULLs. + * Using NC_REQ_ALL in ncmpi_cancel() will cancel all the pending + nonblocking requests. + * Using NC_GET_REQ_ALL or NC_PUT_REQ_ALL in ncmpi_wait_all(), ncmpi_wait(), + and ncmpi_cancel() for all the pending get-only or put-only requests, + respectively. + o Other updates: + * Conform with netCDF on the maximal dimension size for CDF-2 file format + to be (2^32 - 4) + * NC_ERANGE checks have been removed from nc_test for text APIs and + variables that are defined as NC_CHAR type + * Add README.K-Computer build recipe for using Fujitsu MPI compilers on the + K computer at RIKEN in Japan + * Add README.INTEL build recipe for using Intel MPI compilers 4.x + * Build dependency rule is added for files configure and configure.in + * PnetCDF checks MPICC/MPICXX/MPIF77/MPIF90 instead of CC/CXX/F77/F90/FC. + If MPICC/MPICXX/MPIF77/MPIF90 are set, PnetCDF will ignore + CC/CXX/F77/F90/FC. If CC/CXX/F77/F90/FC is set instead of + MPICC/MPICXX/MPIF77/MPIF90, PnetCDF will now copy them to + MPICC/MPICXX/MPIF77/MPIF90. + * Enforce netCDF convention on error code priority: NC_ECHAR trumps + NC_EINVALCOORDS, NC_EEDGE, and NC_ESTRIDE. + * Return error code NC_EGLOBAL instead of NC_ENOTVAR for APIs where using + NC_GLOBAL as the variable ID argument is prohibited. + * All Fortran 77 test and example programs (files with .f and .F + extensions) have been revised to conform with 77 standard, and was tested + using pgf77. + * Now provides a pkg-config file + (http://www.freedesktop.org/wiki/Software/pkg-config/), making it + slightly easier to set the correct pnetcdf include and library paths. + o Bug fixes + * Fix the bus error of invalid address alignment when build with Fujitsu + compiler. See r2171 and r2180. + * Fix the bug for the special case when there is no record variable, the + last fixed-size variable can be larger than 2GiB in size if its starting + file offset is less than 2GiB. See r2166. + * Fix the nonblocking flexible APIs that fail to save (duplicate) the user + MPI derived data type that later is needed to unpack read data to the + user buffer (a call to MPI_Unpack). See r2160. + * Fix Fortran 77 constants nf_fill_uint and nf_fill_int64 (thanks Jim + Edwards) that pgf77-based MPI compiler does not like "_8" modifier. + See r2045 and r2051. The same issue for NAG Fortran compiler is also + resolved. See r2089 and r2093. + * In the example program examples/tutorial/pnetcdf-write-nb.c, the write + buffers used in two iput API calls should be different. See r2095. + * Fix the error reporting mechanism for NC_ERANGE, for when an arithmetic + overflow happens. Overflow checking is now performed before I/O. + +------------------------------------------------------------------- Old: ---- parallel-netcdf-1.6.1.tar.bz2 New: ---- parallel-netcdf-1.7.0.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ parallel-netcdf.spec ++++++ --- /var/tmp/diff_new_pack.Y9PbiN/_old 2016-08-10 21:56:37.000000000 +0200 +++ /var/tmp/diff_new_pack.Y9PbiN/_new 2016-08-10 21:56:37.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package parallel-netcdf # -# Copyright (c) 2015 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -27,7 +27,7 @@ Name: parallel-netcdf %define libname libpnetcdf -Version: 1.6.1 +Version: 1.7.0 Release: 0 %define sonum 1 Summary: High-performance parallel I/O with the NetCDF scientific data format @@ -41,6 +41,7 @@ BuildRequires: flex BuildRequires: gcc-c++ BuildRequires: gcc-fortran +BuildRequires: pkg-config %if 0%{?_openmpi} BuildRequires: openmpi-devel %endif @@ -54,31 +55,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -92,34 +68,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - -Parallel netCDF (PnetCDF) is a library providing high-performance I/O while -still maintaining file-format compatibility with Unidata's NetCDF. - This package contains the openmpi version of utility functions for working with NetCDF files. @@ -133,31 +81,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -174,31 +97,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -215,31 +113,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -255,31 +128,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -289,39 +137,14 @@ %package openmpi-devel Summary: Development files for %{name}-openmpi Group: Development/Libraries/Parallel -Requires: openmpi-devel Requires: %{libname}%{sonum}-openmpi = %{version} +Requires: openmpi-devel %description openmpi-devel NetCDF is a set of software libraries and self-describing, machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -331,39 +154,14 @@ %package mvapich2-devel Summary: Development files for %{name}-mvapich2 Group: Development/Libraries/Parallel -Requires: mvapich2-devel Requires: %{libname}%{sonum}-mvapich2 = %{version} +Requires: mvapich2-devel %description mvapich2-devel NetCDF is a set of software libraries and self-describing, machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -380,31 +178,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -421,31 +194,6 @@ machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. -NetCDF (network Common Data Form) is an interface for array-oriented -data access and a freely-distributed collection of software libraries -for C, Fortran, C++, and perl that provides an implementation of the -interface. The NetCDF library also defines a machine-independent -format for representing scientific data. Together, the interface, -library, and format support the creation, access, and sharing of -scientific data. The NetCDF software was developed at the Unidata -Program Center in Boulder, Colorado. - -NetCDF data is: - - Self-Describing: A NetCDF file includes information about the - data it contains. - - Network-transparent: A NetCDF file is represented in a form that - can be accessed by computers with different ways of storing - integers, characters, and floating-point numbers. - - Direct-access: A small subset of a large dataset may be accessed - efficiently, without first reading through all the preceding - data. - - Appendable: Data can be appended to a NetCDF dataset along one - dimension without copying the dataset or redefining its - structure. The structure of a NetCDF dataset can be changed, - though this sometimes causes the dataset to be copied. - - Sharable: One writer and multiple readers may simultaneously - access the same NetCDF file. - Parallel netCDF (PnetCDF) is a library providing high-performance I/O while still maintaining file-format compatibility with Unidata's NetCDF. @@ -493,7 +241,7 @@ ln -s libpnetcdf.so.%{version} libpnetcdf.so popd -find %{buildroot} -name '*.la' -exec rm {} \; +find %{buildroot} -name '*.la' -delete popd done @@ -538,6 +286,7 @@ %defattr(-,root,root) %{_libdir}/mpi/gcc/openmpi/include/* %{_libdir}/mpi/gcc/openmpi/%{_lib}/*.so +%{_libdir}/mpi/gcc/openmpi/%{_lib}/pkgconfig/pnetcdf.pc %files openmpi-devel-static %defattr(-,root,root) @@ -561,6 +310,7 @@ %defattr(-,root,root,-) %{_libdir}/mpi/gcc/mvapich2/include/* %{_libdir}/mpi/gcc/mvapich2/%{_lib}/*.so +%{_libdir}/mpi/gcc/mvapich2/%{_lib}/pkgconfig/pnetcdf.pc %files mvapich2-devel-static %defattr(-,root,root,-) ++++++ parallel-netcdf-1.6.1-destdir.patch ++++++ --- /var/tmp/diff_new_pack.Y9PbiN/_old 2016-08-10 21:56:37.000000000 +0200 +++ /var/tmp/diff_new_pack.Y9PbiN/_new 2016-08-10 21:56:37.000000000 +0200 @@ -1,6 +1,6 @@ diff -ru a/man/Makefile.in b/man/Makefile.in ---- a/man/Makefile.in 2013-11-17 06:18:16.000000000 +0100 -+++ b/man/Makefile.in 2015-07-15 15:59:02.004676983 +0200 +--- a/man/Makefile.in ++++ b/man/Makefile.in @@ -43,12 +43,12 @@ test: @@ -17,26 +17,30 @@ uninstall: diff -ru a/src/lib/Makefile.in b/src/lib/Makefile.in ---- a/src/lib/Makefile.in 2015-02-12 08:34:35.000000000 +0100 -+++ b/src/lib/Makefile.in 2015-07-15 12:47:05.068911386 +0200 -@@ -85,10 +85,10 @@ +--- a/src/lib/Makefile.in ++++ b/src/lib/Makefile.in +@@ -93,12 +93,12 @@ $(RANLIB) $(LIBRARY) - install: + install: $(LIBRARY) - $(INSTALL) -d -m 755 $(LIBDIR) - $(INSTALL_DATA) $(LIBRARY) $(LIBDIR)/$(LIBRARY) - $(INSTALL) -d -m 755 $(INCDIR) - $(INSTALL_DATA) $(HEADER) $(INCDIR)/$(HEADER) +- $(INSTALL) -d -m 755 $(LIBDIR)/pkgconfig +- $(INSTALL_DATA) $(PKGCONFIG) $(LIBDIR)/pkgconfig/$(PKGCONFIG) + $(INSTALL) -d -m 755 $(DESTDIR)$(LIBDIR) + $(INSTALL_DATA) $(LIBRARY) $(DESTDIR)$(LIBDIR)/$(LIBRARY) + $(INSTALL) -d -m 755 $(DESTDIR)$(INCDIR) + $(INSTALL_DATA) $(HEADER) $(DESTDIR)$(INCDIR)/$(HEADER) ++ $(INSTALL) -d -m 755 $(DESTDIR)$(LIBDIR)/pkgconfig ++ $(INSTALL_DATA) $(PKGCONFIG) $(DESTDIR)$(LIBDIR)/pkgconfig/$(PKGCONFIG) uninstall: - $(RM) -f $(LIBDIR)/$(LIBRARY) + $(RM) -f $(LIBDIR)/pkgconfig/$(PKGCONFIG) diff -ru a/src/libcxx/Makefile.in b/src/libcxx/Makefile.in ---- a/src/libcxx/Makefile.in 2014-10-31 05:49:15.000000000 +0100 -+++ b/src/libcxx/Makefile.in 2015-07-15 15:36:58.655923601 +0200 +--- a/src/libcxx/Makefile.in ++++ b/src/libcxx/Makefile.in @@ -71,8 +71,8 @@ ) ; done @@ -49,8 +53,8 @@ uninstall: $(RM) -f $(INCDIR)/$(CXX_HEADER) diff -ru a/src/libf/Makefile.in b/src/libf/Makefile.in ---- a/src/libf/Makefile.in 2015-02-18 18:14:26.000000000 +0100 -+++ b/src/libf/Makefile.in 2015-07-15 15:49:14.637190697 +0200 +--- a/src/libf/Makefile.in ++++ b/src/libf/Makefile.in @@ -391,8 +391,8 @@ $(SED) -e "s%/\*%!%g" -e "s%\*/%%g" $< > $@ @@ -63,12 +67,12 @@ uninstall: $(RM) -f $(INCDIR)/pnetcdf.inc diff -ru a/src/libf90/Makefile.in b/src/libf90/Makefile.in ---- a/src/libf90/Makefile.in 2014-10-11 06:19:56.000000000 +0200 -+++ b/src/libf90/Makefile.in 2015-07-15 12:50:01.283319078 +0200 +--- a/src/libf90/Makefile.in ++++ b/src/libf90/Makefile.in @@ -69,8 +69,8 @@ - $(COMPILE.F90) $(srcdir)/pnetcdf.f90 + $(PNETCDF_MOD): $(SRCS) - install: + install: $(PNETCDF_MOD) - $(INSTALL) -d -m 755 $(INCDIR) - $(INSTALL_DATA) $(PNETCDF_MOD) $(INCDIR) + $(INSTALL) -d -m 755 $(DESTDIR)$(INCDIR) @@ -77,8 +81,8 @@ uninstall: $(RM) -f $(INCDIR)/$(PNETCDF_MOD) diff -ru a/src/utils/ncmpidiff/Makefile.in b/src/utils/ncmpidiff/Makefile.in ---- a/src/utils/ncmpidiff/Makefile.in 2014-05-14 07:22:20.000000000 +0200 -+++ b/src/utils/ncmpidiff/Makefile.in 2015-07-15 12:50:27.337935753 +0200 +--- a/src/utils/ncmpidiff/Makefile.in ++++ b/src/utils/ncmpidiff/Makefile.in @@ -34,11 +34,11 @@ $(LINK.c) $(OBJS) $(LDFLAGS) $(LIBS) @@ -96,8 +100,8 @@ uninstall: $(RM) -f $(BINDIR)/$(PROGRAM) diff -ru a/src/utils/ncmpidump/Makefile.in b/src/utils/ncmpidump/Makefile.in ---- a/src/utils/ncmpidump/Makefile.in 2014-05-14 07:22:20.000000000 +0200 -+++ b/src/utils/ncmpidump/Makefile.in 2015-07-15 12:50:44.176688011 +0200 +--- a/src/utils/ncmpidump/Makefile.in ++++ b/src/utils/ncmpidump/Makefile.in @@ -45,11 +45,11 @@ echo "*** $(PROGRAM) test successful ***" @@ -115,8 +119,8 @@ uninstall: $(RM) -f $(BINDIR)/$(PROGRAM) diff -ru a/src/utils/ncmpigen/Makefile.in b/src/utils/ncmpigen/Makefile.in ---- a/src/utils/ncmpigen/Makefile.in 2015-05-29 20:52:08.000000000 +0200 -+++ b/src/utils/ncmpigen/Makefile.in 2015-07-15 12:52:59.178701649 +0200 +--- a/src/utils/ncmpigen/Makefile.in ++++ b/src/utils/ncmpigen/Makefile.in @@ -47,11 +47,11 @@ test: $(PROGRAM) b-test c-test FORCE @@ -134,8 +138,8 @@ uninstall: $(RM) -f $(BINDIR)/$(PROGRAM) diff -ru a/src/utils/ncmpivalid/Makefile.in b/src/utils/ncmpivalid/Makefile.in ---- a/src/utils/ncmpivalid/Makefile.in 2014-05-14 07:22:20.000000000 +0200 -+++ b/src/utils/ncmpivalid/Makefile.in 2015-07-15 13:16:12.645642938 +0200 +--- a/src/utils/ncmpivalid/Makefile.in ++++ b/src/utils/ncmpivalid/Makefile.in @@ -34,11 +34,11 @@ $(LINK.c) $(OBJS) $(LDFLAGS) $(LIBS) @@ -152,20 +156,37 @@ uninstall: $(RM) -f $(BINDIR)/$(PROGRAM) -diff -ru a/src/utils/pnetcdf_version/Makefile.in b/src/utils/pnetcdf_version/Makefile.in ---- a/src/utils/pnetcdf_version/Makefile.in 2014-05-14 07:22:20.000000000 +0200 -+++ b/src/utils/pnetcdf_version/Makefile.in 2015-07-15 13:23:20.325594222 +0200 -@@ -35,11 +35,11 @@ - $(LINK.c) $(OBJS) +diff -ru a/src/utils/ncoffsets/Makefile.in b/src/utils/ncoffsets/Makefile.in +--- a/src/utils/ncoffsets/Makefile.in ++++ b/src/utils/ncoffsets/Makefile.in +@@ -25,10 +25,10 @@ + $(SEQ_CC) -o $@ $< install: $(PROGRAM) $(MANUAL) - $(INSTALL) -d -m 755 $(MANDIR)/man1 - $(INSTALL_DATA) $(srcdir)/$(MANUAL) $(MANDIR)/man1/$(MANUAL) +- $(INSTALL) -d $(BINDIR) +- $(INSTALL) -m 755 $(PROGRAM) $(BINDIR)/$(PROGRAM) + $(INSTALL) -d -m 755 $(DESTDIR)$(MANDIR)/man1 + $(INSTALL_DATA) $(srcdir)/$(MANUAL) $(DESTDIR)$(MANDIR)/man1/$(MANUAL) ++ $(INSTALL) -d $(DESTDIR)$(BINDIR) ++ $(INSTALL) -m 755 $(PROGRAM) $(DESTDIR)$(BINDIR)/$(PROGRAM) + + uninstall: + $(RM) -f $(BINDIR)/$(PROGRAM) +diff -ru a/src/utils/pnetcdf_version/Makefile.in b/src/utils/pnetcdf_version/Makefile.in +--- a/src/utils/pnetcdf_version/Makefile.in ++++ b/src/utils/pnetcdf_version/Makefile.in +@@ -41,10 +41,10 @@ + $(SEQ_CC) $(DEFS) -o $@ $< + install: $(PROGRAM) $(MANUAL) +- $(INSTALL) -d -m 755 $(MANDIR)/man1 +- $(INSTALL_DATA) $(srcdir)/$(MANUAL) $(MANDIR)/man1/$(MANUAL) - $(INSTALL) -d $(BINDIR) - $(INSTALL) -m 755 $(PROGRAM) $(BINDIR)/$(PROGRAM) ++ $(INSTALL) -d -m 755 $(DESTDIR)$(MANDIR)/man1 ++ $(INSTALL_DATA) $(srcdir)/$(MANUAL) $(DESTDIR)$(MANDIR)/man1/$(MANUAL) + $(INSTALL) -d $(DESTDIR)$(BINDIR) + $(INSTALL) -m 755 $(PROGRAM) $(DESTDIR)$(BINDIR)/$(PROGRAM) ++++++ parallel-netcdf-1.6.1.tar.bz2 -> parallel-netcdf-1.7.0.tar.bz2 ++++++ ++++ 73361 lines of diff (skipped)
