On Wed, 16 Feb 2000, James Henstridge wrote:
> If it bombed out here, then aclocal must have bombed. But since you
> haven't included the errors aclocal gave, I can't say how to fix it.
Here is the complete output of autogen.sh - is the sed error the one I
should be worried about (it says to ignore non-fatal messages)?
bash-2.03$ ./autogen.sh
I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command line.
Running gettextize... Ignore non-fatal messages.
sed: can't read aclocal.m4: No such file or directory
You should update your own `aclocal.m4' by adding the necessary
macro packages gettext.m4, lcmessage.m4 and progtest.m4 from
the directory `/aclocal'
Running libtoolize
You should add the contents of `/usr/share/aclocal/libtool.m4' to
`aclocal.m4'.
aclocal: configure.in: 116: macro `AM_PATH_GDK_IMLIB' not found in
library
loading cache ./config.cache
./configure: line 531: syntax error near unexpected token
`AM_INIT_AUTOMAKE(dia,'
./configure: line 531: `AM_INIT_AUTOMAKE(dia, 0.83)'
Now type 'make' to compile dia.
> The problem is probably due to a missing macro file, which may occur if
> you don't have the appropriate package or development portion of a package
> installed.
Thanks - how can I pin this error message down to one particular
package? I've got gdk-imlib-dev installed, so the line:
aclocal: configure.in: 116: macro `AM_PATH_GDK_IMLIB' not found in
library
may not be the problem, although it does look like a likely suspect.
Is there any more information I can send that would be helpful?
Thanks,
Brian Jepson * ([EMAIL PROTECTED]) * http://users.ids.net/~bjepson
