Tim Wallace <twallace@ll.mit.edu> writes:
> Version: 9.0.3
> after successful configure, make fails if you have the env var "U" set.
> It fails almost immediately in the src/port directory with a
> nonsensical error message involving the contents of the "U" var. Unset
> U and everything built fine.
So far as I can find, there is no reference to a symbol "U" in any of our
makefiles. However, there is this bit in the configure script:
ac_libobjs=
ac_ltlibobjs=
for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue
# 1. Remove the extension, and $U if already installed.
ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
ac_i=`$as_echo "$ac_i" | sed "$ac_script"`
# 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR
# will be set to the directory where LIBOBJS objects are built.
ac_libobjs="$ac_libobjs \${LIBOBJDIR}$ac_i\$U.$ac_objext"
ac_ltlibobjs="$ac_ltlibobjs \${LIBOBJDIR}$ac_i"'$U.lo'
done
LIBOBJS=$ac_libobjs
LTLIBOBJS=$ac_ltlibobjs
I have no idea what that's trying to do, but maybe it gets confused
if U has an existing definition. Suggest you file a bug against
autoconf.
regards, tom lane
