[Octave-bug-tracker] [bug #30721] Can't build tip on FreeBSD

[Rik]

Follow-up Comment #7, bug #30721 (project octave):

I think you're pretty close to solving this.

The toolchain set uses Automake to create Makefile.in files from Makefile.am
and then configure to create Makefile from Makefile.in.

The jam seems to be your Automake version.  From your log output, as pointed
out by Judd,

configure.ac:53: version mismatch. This is Automake 1.11.1,
configure.ac:53: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:53: comes from Automake 1.10.1. You should recreate
configure.ac:53: aclocal.m4 with aclocal and run automake again.

When Automake runs in a fresh directory it either symlinks or copies certain
configuration files from its repository to the local directory.  If you check
the script bootstrap:754 you will see that Octave chooses the copy option. 
The critical thing to note is that this copying only happens on a virgin
directory.  Once you have run Automake once in a directory it no longer needs
to copy over the library stuff, but only create Makefile.in.

My suspicion is that you ran automake-1.10 in the directory, discovered it
was not the required version, and then ran automake-1.11.  Unfortunately, at
this point the directory is poisoned with 1.10 files and no amount of
re-running automake-1.11 will cure it.  

I've had this happen on a different autotools-based project and the simplest
thing to do was to start over.  I don't believe that aclocal.m4 is the only
file which needs regeneration.

So, my advice is:
1) Use 'hg clone' to create a virgin source code directory.
2) Modify autogen.sh to ensure automake-1.11 is called.
3) Run autogen.sh and collect the logs just in case I'm wrong.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30721>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/