[Nexus-developers] Re: NXopenpath, autoconf

[Akeroyd, FA (Freddie)]

Hi Mark,

> 
>   Now, the autoconf stuff. It simply does not work for me. First I had
>   to install all the newest autotools to get going at all. Then
>   autogen.sh created a lot of error messages about libtool. I got around
>   this by pasting the contents of libtool.m4 into acinclude.m4. I found
>   this idea on the WWW. Then I got a configure script.
> 
>   My suggestion: common usage is to include the configure script, we
>   should do the same.
> 
The configure script is included in distributions, not necessarily in
development versions straight from CVS (that's my understanding anyway). The
reason for this is that your local "configure" will get updated whenever you
run autoconf, you may not be using the same version that somebody else is,
and so you can be shown as in "conflict" with the CVS version when you are
not really. You can put configure into CVS, but you have to know a bit about
CVS conflict resolution, so it's easier not to.

>   The configure script processed without further errors. But compiling did
>   not work: it complained about a file libNexus.la missing. I then
>   proceeded to compile the test program manually.
> 
>   This is against both Tru64Unix 5.1 and Redhat 7.3. I built the configure
>   script on the latter.
> 
I have ran the default redhat 9 version of autotools and also built and used
the latest versions; all worked without problem. Maybe it's a Redhat issue -
version 7.3 is quite old and they may not have checked recent libtools etc.
on it. If you edit autogen.sh to allow any version of autotools, and then
use the default ones for redhat 7.3, are things any better?

Freddie