On 8/03/2013 9:15 PM, Erik Joelsson wrote:
Could it be that bash is somehow resetting your path when you launch it?
I can't see how. Yet I've annotated my copy and it is not being
executed. ???
Totally baffled. And rather peeved. This is a big waste of time.
Thanks,
David
/Erik
On 2013-03-08 06:06, David Holmes wrote:
My build machine has autoconf 2.68 in /usr/bin but others use 2.67.
This means we keep getting differences in generated-configure.sh that
are not related to actual changes.
So I put the 2.67 version of autoconf first in my path:
> which autoconf
/home/dholmes/bin/autoconf
> autoconf -V
autoconf (GNU Autoconf) 2.67
but when I run autogen.sh (which simply calls "autoconf") the
resulting file has:
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.68 for OpenJDK jdk8.
???
How can I use 2.67 without having to actually downgrade it on a shared
build machine ? :(
I've even tried copying autom4te to ~/bin and hacking the scripts
directly. But I still get autoconf 2.68 ??? Makes no sense.
Thanks,
David
