Re: [Swarm-Support] Compiling Swarm-2.2 on Solaris 2.8

[Gary Polhill]

Here's the output... Should I start again from scratch (i.e. a fresh download)

% ./autogen.sh

**Warning**: only tested with version 1.9.3
of automake and may not work with version 1.9.6
processing .
Running aclocal  -I m4 -I . ...
Running autoheader...
Running autoconf ...
configure.in:15: error: possibly undefined macro: LT_AC_PROG_SED
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:30: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
configure.in:31: error: possibly undefined macro: AC_PROG_LIBTOOL
Running automake --gnu  ...
src/Makefile.am:34: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:34: 
src/Makefile.am:34: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/Makefile.am:34: to `configure.in' and run `aclocal' and `autoconf' again.
src/activity/Makefile.am:14: Libtool library used but `LIBTOOL' is undefined
src/activity/Makefile.am:14: 
src/activity/Makefile.am:14: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/activity/Makefile.am:14: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/analysis/Makefile.am:13: Libtool library used but `LIBTOOL' is undefined
src/analysis/Makefile.am:13: 
src/analysis/Makefile.am:13: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/analysis/Makefile.am:13: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/collections/Makefile.am:13: Libtool library used but `LIBTOOL' is undefined
src/collections/Makefile.am:13: 
src/collections/Makefile.am:13: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/collections/Makefile.am:13: to `configure.in' and run `aclocal' and 
`autoconf' again.
src/defobj/Makefile.am:17: Libtool library used but `LIBTOOL' is undefined
src/defobj/Makefile.am:17: 
src/defobj/Makefile.am:17: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/defobj/Makefile.am:17: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/misc/Makefile.am:13: Libtool library used but `LIBTOOL' is undefined
src/misc/Makefile.am:13: 
src/misc/Makefile.am:13: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/misc/Makefile.am:13: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/objectbase/Makefile.am:11: Libtool library used but `LIBTOOL' is undefined
src/objectbase/Makefile.am:11: 
src/objectbase/Makefile.am:11: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/objectbase/Makefile.am:11: to `configure.in' and run `aclocal' and 
`autoconf' again.
src/random/Makefile.am:15: Libtool library used but `LIBTOOL' is undefined
src/random/Makefile.am:15: 
src/random/Makefile.am:15: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/random/Makefile.am:15: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/simtools/Makefile.am:13: Libtool library used but `LIBTOOL' is undefined
src/simtools/Makefile.am:13: 
src/simtools/Makefile.am:13: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/simtools/Makefile.am:13: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/simtoolsgui/Makefile.am:13: Libtool library used but `LIBTOOL' is undefined
src/simtoolsgui/Makefile.am:13: 
src/simtoolsgui/Makefile.am:13: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/simtoolsgui/Makefile.am:13: to `configure.in' and run `aclocal' and 
`autoconf' again.
src/space/Makefile.am:13: Libtool library used but `LIBTOOL' is undefined
src/space/Makefile.am:13: 
src/space/Makefile.am:13: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/space/Makefile.am:13: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/swarmgstep/Makefile.am:27: Libtool library used but `LIBTOOL' is undefined
src/swarmgstep/Makefile.am:27: 
src/swarmgstep/Makefile.am:27: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/swarmgstep/Makefile.am:27: to `configure.in' and run `aclocal' and 
`autoconf' again.
src/tclobjc/Makefile.am:28: Libtool library used but `LIBTOOL' is undefined
src/tclobjc/Makefile.am:28: 
src/tclobjc/Makefile.am:28: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/tclobjc/Makefile.am:28: to `configure.in' and run `aclocal' and `autoconf' 
again.
src/tkobjc/Makefile.am:28: Libtool library used but `LIBTOOL' is undefined
src/tkobjc/Makefile.am:28: 
src/tkobjc/Makefile.am:28: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
src/tkobjc/Makefile.am:28: to `configure.in' and run `aclocal' and `autoconf' 
again.
processing ./avcall
Running aclocal  -I m4 -I . ...
Running autoconf ...
skipping automake in ./avcall -- Makefile.am does not exist
processing ./libobjc
Running aclocal  -I m4 -I . ...
Running autoheader...
Running autoconf ...
configure.in:11: error: possibly undefined macro: LT_AC_PROG_SED
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:37: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
configure.in:38: error: possibly undefined macro: AC_PROG_LIBTOOL
Running automake --gnu  ...
Makefile.am:17: Libtool library used but `LIBTOOL' is undefined
Makefile.am:17: 
Makefile.am:17: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
Makefile.am:17: to `configure.in' and run `aclocal' and `autoconf' again.
Skipping configure process.


>>> address@hidden 2006-06-09 14:32:03 >>>
Gary Polhill wrote:
> OK... This is all a bit new to me. I've obtained the latest version from CVS. 
> There's no configure script, so I ran aclocal then autoconf. I got the 
> following errors [...]
>   
Try ./autogen.sh at the top level..  It may warn you that you have old 
or new versons of the various tools.   But you shouldn't get many 
warnings (the libtool ones you got should go away).
_______________________________________________
Support mailing list
address@hidden 
http://www.swarm.org/mailman/listinfo/support

-- 
Please note that the views expressed in this e-mail are those of the
sender and do not necessarily represent the views of the Macaulay
Institute. This email and any attachments are confidential and are
intended solely for the use of the recipient(s) to whom they are
addressed. If you are not the intended recipient, you should not read,
copy, disclose or rely on any information contained in this e-mail, and
we would ask you to contact the sender immediately and delete the email
from your system. Thank you.
Macaulay Institute and Associated Companies, Macaulay Drive,
Craigiebuckler, Aberdeen, AB15 8QH.