h5edit test/Makefile.am shows 'check_PROGRAMS' recursively defined

With apologies if this list is the wrong place to ask h5edit
(http://www.hdfgroup.org/projects/npoess/jpss_downloads.html)
questions...

h5edit.1.0.0.tar.gz (md5sum 065013585cc483fa7cd945020e3d967f) shows
the fatal error
   test/Makefile.am:22: variable `check_PROGRAMS' recursively defined
after configure when 'make' is invoked. Modifying test/Makefile.am to read
   check_PROGRAMS= $(EXTRA_TEST)
fixes that issue. 'make check' seems to check nothing.

Are these details as expected? Have others built and tested h5edit as shipped?

Also, it seems odd that 'Makefile.am' has been shipped with the source
tarball. Finally, AC_INIT in h5edit seems to omit the final ".0" in
the "1.0.0" version.

- Rhys

Hi Rhys,

Could you tell me more about the machine you test h5edit on?
For example, "uname -a" output, compilers used. Thanks.

-Albert
h5edit developer

···

On 9/12/2011 4:05 PM, Rhys Ulerich wrote:

With apologies if this list is the wrong place to ask h5edit
(http://www.hdfgroup.org/projects/npoess/jpss_downloads.html)
questions...

h5edit.1.0.0.tar.gz (md5sum 065013585cc483fa7cd945020e3d967f) shows
the fatal error
    test/Makefile.am:22: variable `check_PROGRAMS' recursively defined
after configure when 'make' is invoked. Modifying test/Makefile.am to read
    check_PROGRAMS= $(EXTRA_TEST)
fixes that issue. 'make check' seems to check nothing.

Are these details as expected? Have others built and tested h5edit as shipped?

Also, it seems odd that 'Makefile.am' has been shipped with the source
tarball. Finally, AC_INIT in h5edit seems to omit the final ".0" in
the "1.0.0" version.

- Rhys

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

Hi Albert,

h5edit.1.0.0.tar.gz (md5sum 065013585cc483fa7cd945020e3d967f) shows
the fatal error
  test/Makefile.am:22: variable `check_PROGRAMS' recursively defined
after configure when 'make' is invoked. Modifying test/Makefile.am to read
  check_PROGRAMS= $(EXTRA_TEST)
fixes that issue. 'make check' seems to check nothing.

Could you tell me more about the machine you test h5edit on?
For example, "uname -a" output, compilers used. Thanks.

Sure. Thanks for looking into it.

$ uname -a
Linux setun 2.6.32-31-generic #60-Ubuntu SMP Thu Mar 17 22:15:39 UTC
2011 x86_64 GNU/Linux

$ gcc --version
gcc (GCC) 4.5.1

$ automake --version
automake (GNU automake) 1.11.1

$ autoconf --version
autoconf (GNU Autoconf) 2.68

Also, I used CC=h5pcc (from a parallel build of HDF5). FWIW, this
problem doesn't seem build-system version-dependent to me. I suspect
the problem is a mixture of stale development artifacts lingering in
the source tree.

- Rhys

Hi Rhys,
I discovered that I have forgot to include an autoconfigure related file in the
release tarball that will cause some problems during the "make" stage. But
the error should not be fatal. Are you able to do the following build and installation
stage?

1) % ./configure # assuming h5cc is in your $PATH
2) % gmake # some non-fatal error messages
3) % gmake check # to run tests
4) % gmake prefix=<install-path> # install h5edit in <install-path>/bin

If it does not work for you, could you please email me (acheng@hdfgroup.org) the output
of the above commands (or whatever commands you used)?
Thanks.

-Albert
h5edit developer

···

On 9/13/2011 11:02 AM, Rhys Ulerich wrote:

Hi Albert,

h5edit.1.0.0.tar.gz (md5sum 065013585cc483fa7cd945020e3d967f) shows
the fatal error
   test/Makefile.am:22: variable `check_PROGRAMS' recursively defined
after configure when 'make' is invoked. Modifying test/Makefile.am to read
   check_PROGRAMS= $(EXTRA_TEST)
fixes that issue. 'make check' seems to check nothing.
       
Could you tell me more about the machine you test h5edit on?
For example, "uname -a" output, compilers used. Thanks.
     

Sure. Thanks for looking into it.

$ uname -a
Linux setun 2.6.32-31-generic #60-Ubuntu SMP Thu Mar 17 22:15:39 UTC
2011 x86_64 GNU/Linux

$ gcc --version
gcc (GCC) 4.5.1

$ automake --version
automake (GNU automake) 1.11.1

$ autoconf --version
autoconf (GNU Autoconf) 2.68

Also, I used CC=h5pcc (from a parallel build of HDF5). FWIW, this
problem doesn't seem build-system version-dependent to me. I suspect
the problem is a mixture of stale development artifacts lingering in
the source tree.

- Rhys