./configure --with-hdf4 fails, but ./configure --with-hdf4=/usr/lib works

[Even Rouault]

Without path:

./configure --without-libtool --with-hdf4 [SNIP]

In GDALmake.opt
LIBS    =      [SNIP] -L -lmfhdf -ldf [SNIP]

In the report at end of configure, hdf4 is indicated as being build, but the "-L -lmfhdf -ldf" in the LIBS line is wrong.

With path:

./configure --without-libtool --with-hdf4=/usr/lib [SNIP]

LIBS    =    [SNIP] -L/usr/lib -lmfhdf [SNIP]

correct, and builds fine

Interesting, this is a trunk only problem. With branches/1.5 svn, ./configure --with-hdf4 works

[Even Rouault]

By doing a diff on both configure.in, there are clearly changes. The configure.in in trunk looks suspicious for the --with-hdf4 case

  if test x"$with_hdf4" = x"yes" -o x"$with_hdf4" = x"" ; then
    HDF_LIB_DIR=""
  else
    if test -d $with_hdf4/lib ; then
      HDF_LIB_DIR="$with_hdf4/lib"
    else
      HDF_LIB_DIR="$with_hdf4"
    fi
  fi

  ORIG_LIBS="$LIBS"
  LIBS="-L$HDF_LIB_DIR $LIBS"

[Even Rouault]

Ok, I've fixed configure.in in r15505. I've tested successfully ./configure --with-hdf4, ./configure --with-hdf4=yes, ./configure --with-hdf4=/usr and ./configure --with-hdf4=/usr/lib

configure needs to be regenerated

[warmerdam]

regenerated (r15506). Is this change something that belongs in 1.5 as well?

[Even Rouault]

tanks. no, this is trunk only. This was a regression apparently