autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AC_LIBOBJ problem?


From: Harlan Stenn
Subject: AC_LIBOBJ problem?
Date: Sat, 20 Dec 2003 01:58:58 -0500
User-agent: EMH/1.10.0 SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd)

I haven't looked at this hard.

tftp-hpa's configure.in has a line that looks like this:

 AC_SEARCH_LIBS(xmalloc, iberty, , LIBXTRA=true [AC_LIBOBJ(xmalloc)])

Under autoconf-2.53 this eventually produced:

 LIBXTRA=true LIBOBJS="$LIBOBJS xmalloc.$ac_objext"

while under autoconf-2.58 and -2.59 it produces:

 LIBXTRA=true case $LIBOBJS in
    "xmalloc.$ac_objext"   | \
  *" xmalloc.$ac_objext"   | \
    "xmalloc.$ac_objext "* | \
  *" xmalloc.$ac_objext "* ) ;;
  *) LIBOBJS="$LIBOBJS xmalloc.$ac_objext" ;;
 esac

and I see this on ome of my machines:

 ...
 tftp-hpa-0.28/configure: line 11526: syntax error near unexpected token `)'
 tftp-hpa-0.28/configure:
 line 11526: `  *" xmalloc.$ac_objext "* ) ;;'
 gmake: *** [foo] Error 2

the target machine is a redhat 7.3 box.

While I'm digging to find the root cause, I wondered if it wouldn't be
better in general if the test was something more like:

 LIBXTRA=true case " $LIBOBJS " in
  *" xmalloc.$ac_objext "* ) ;;
  *) LIBOBJS="$LIBOBJS xmalloc.$ac_objext" ;;
 esac

And I have vague recollections of several older shells hating something that
looked like that...

H (who may be too tired to think right now...)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]