Opened 16 years ago
Closed 16 years ago
#424 closed defect (wontfix)
AC_CONFIG_AUX_DIR added in configure.in of 6.4.x causes rpmbuild failure
Reported by: | neteler | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 6.4.0 |
Component: | Default | Version: | 6.4.0 RCs |
Keywords: | Cc: | ||
CPU: | All | Platform: | Linux |
Description
The following addition to configure.in of 6.4.x:
diff -u ~/grass63_release/configure.in configure.in --- /home/neteler/grass63_release/configure.in 2008-03-26 16:04:27.000000000 +0100 +++ configure.in 2008-09-12 23:02:45.000000000 +0200 @@ -99,6 +99,10 @@ AC_SUBST(ARCH) +# Use absolute path for aux directory so that install-sh works + +AC_CONFIG_AUX_DIR($SRCDIR) + # Set GISBASE and GRASS_BIN GISBASE=${WINDSTDIR}/dist.${ARCH}
leads to this error when creating a (Mandriva) RPM from 6.4.0RC1:
rpmbuild -ba grass640RC1.specExecuting(%prep): /bin/sh -e /var/tmp/rpm-tmp.40668 + umask 022 + cd /usr/src/rpm/BUILD ... + LDFLAGS='-L/usr/X11R6/lib64 -Wl,--as-needed -Wl,--no-undefined' + export LDFLAGS + CONFIGURE_TOP=. + /usr/lib/rpm/manbo/force-as-needed-for-shared-lib-in-libtool Forcing -Wl,--as-needed in configure/libtool to workaround libtool bug (cf http://lists.gnu.org/archive/html/libtool-patches/2004-06/msg00002.html) + /usr/lib/rpm/manbo/drop-ld-no-undefined-for-shared-lib-modules-in-libtool + cputoolize -c . libtoolize: cannot handle variables in AC_CONFIG_AUX_DIR error: Bad exit status from /var/tmp/rpm-tmp.16786 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.16786 (%build)
Do we really need AC_CONFIG_AUX_DIR (e.g., in GRASS 6.3 it wasn't needed) or can it be conditionalized?
Markus
Change History (3)
comment:1 by , 16 years ago
follow-up: 3 comment:2 by , 16 years ago
Replying to neteler:
The following addition to configure.in of 6.4.x:
+AC_CONFIG_AUX_DIR($SRCDIR)
leads to this error when creating a (Mandriva) RPM from 6.4.0RC1:
+ cputoolize -c .
libtoolize: cannot handle variables in AC_CONFIG_AUX_DIR
This looks like a problem with the RPM spec file. GRASS doesn't use libtool. The build process shouldn't be concerning itself with the contents of those scripts, just running configure.
Do we really need AC_CONFIG_AUX_DIR (e.g., in GRASS 6.3 it wasn't needed) or can it be conditionalized?
It's needed, and I don't think that it can be conditionalised.
comment:3 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
It was added in r32168