Follow-up Comment #5, sr #110397 (project autoconf):
Yes, of course. That makes sense. I'll need to look into finding you a machine
for remote shell access.
However, the build scripts for automake and autoconf are very simple. For
automake, it (essentially) runs these commands in the build directory:
export PERL=/usr/bin/perl
./configure --prefix=$prefix
make install
Similarly, for autoconf:
export PERL=/usr/bin/perl
sed -i 's/libtoolize/glibtoolize/g' bin/autoreconf.in
sed -i 's/libtoolize/glibtoolize/g' man/autoreconf.1
./configure --prefix=$prefix --with-lispdir=$elisp
make install
rm -f info/standards.info
The modification to autoreconf.in is so that autoreconf uses Homebrew's (GNU)
libtool instead of Apple's libtool. Could the patch to autoreconf.{in,1} be
causing problems?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110397>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
