On Sun, 17 Sep 2006, [log in to unmask] wrote:
> I've been trying for ages to get Starlink working on various Linux
> distros. I'm not very familiar with how package dependencies work and I
> keep running into all sorts of problems. I just recently set up an
> ASMD-64 system and I have installed Ubuntu 6.06.1. When I try to
> bootstrap Starlink I get the following error :
>
> m4 at /usr/bin/m4 is OK
> Bootstrapping with
> STARCONF_DEFAULT_STARLINK = /aspersa/scuba2/star64
> STARCONF_DEFAULT_PREFIX = /aspersa/scuba2/star64
> BUILDSUPPORT_PREFIX = /aspersa/scuba2/star64/buildsupport
> Do we need to build GNU m4? false
> ln -s buildsupport/starconf/componentinfo.dtd componentinfo.dtd
> Bootstrapping buildsupport:
> make -f Makefile.tmp \
> prefix=/aspersa/scuba2/star64/buildsupport \
> MANIFESTS=/aspersa/scuba2/star64/manifests \
> buildsupport
> cd buildsupport/starconf && autoreconf --install --symlink --verbose
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> autoreconf: running: aclocal
> NONE:0: /usr/bin/m4: `changeword' from frozen file not found in builtin
> table!
> autom4te: /usr/bin/m4 failed with exit status: 1
> aclocal: autom4te failed with exit status: 1
> autoreconf: aclocal failed with exit status: 1
> make: *** [buildsupport/starconf/configure] Error 1
> Failed to make buildsupport
Hi Jen,
I've had a look for related problems with Ubuntu and this issue is seen
from time-to-time. The consensus is this is because the version of m4 (a
macro preprocessor) used is compiled without support for the "changeword"
builtin. What's not clear is why this matters, but it may be used when
automake is built.
Looking at this log I don't see any sign of automake being built, so I
suspect you've already done that part, maybe it also failed in some
fashion? That would be interesting to see.
The fact that a frozen builtin is not found might suggest that you've
managed to switch versions of automake, so check that you have the
"/aspersa/scuba2/star64/buildsupport/bin" directory first on your PATH,
otherwise you'll pick up automake from the system directories.
When you've checked your PATH make sure that any files with suffix ".m4f"
are removed from the buildsupport/ directory tree and try:
./bootstrap --buildsupport
in the top-level directory. Since Tim used Ubuntu for the Keoe 64bit
build, this must be possible.
Regards,
Peter.
--
Dr. Peter W. Draper, http://star-www.dur.ac.uk/~pdraper
|