On Wed, Mar 13, 2019 at 5:20 PM William A Rowe Jr <[email protected]> wrote: > > I think this comes from; > > AC_LIBTOOL_WIN32_DLL > AC_PROG_LIBTOOL > # get libtool's setting of shlibpath_var > eval `grep "^shlibpath_var=[[A-Z_]]*$" $apr_builddir/libtool` > if test "x$shlibpath_var" = "x"; then > shlibpath_var=REPLACE_WITH_YOUR_SHLIBPATH_VAR > fi > > The assignment of shlibpath_var within an eval isn't promoted into the > current env table, right?
Hmm, should be working: $ sh -x $ eval `grep '^shlibpath_var=[A-Z_]*$' ./libtool` + grep ^shlibpath_var=[A-Z_]*$ ./libtool + eval shlibpath_var=LD_LIBRARY_PATH + shlibpath_var=LD_LIBRARY_PATH $ ^D > This code following AC_PROG_LIBTOOL appears to be a no--op unless I'm missing > something obvious. The grep-ed double square brackets look weird to me, does not work with my (ba)sh at least, so doesn't it enter the REPLACE_WITH_YOUR_SHLIBPATH_VAR path anytime? Also grep is possibly missing 2>/dev/null to silence ./configure a bit.
