On Sat, 6 Sep 2003, Mike Bosschaert wrote:
> Yep, it's there: /usr/share/aclocal/glib.m4
Ok - just one of those things worth double checking. Looking at
the errors again I suspect the problem in somehow in the autoconf
and/or automake setup
> yes ./configure: line 1047: AM_OUTPUT_DEPENDENCY_COMMANDS: command not
> found ./configure: line 1115: AC_GNU_SOURCE: command not found
Those macros aren't being substituted for and that results in
./configure having those as "commands" to run.
AM_OUTPUT_DEPENDENCY_COMMANDS is used on line 14 of configure.in
and AC_GNU_SOURCE is used on line 49.
> automake 1.7.5
> autoconf 2.13; 2.57 is also installed, tried that as well, same output and
> messages
>
> Any other options?
As long as we're grasping at straws (and this is the first time
I've heard of this problem)...
In /usr/share/aclocal is there any file which defines the macro
AM_OUTPUT_DEPENDENCY_COMMANDS? In my setup that is defined in
depend.m4
AC_GNU_SOURCE is defined, as far as I can see, in the file
.../share/autoconf/autoconf/specific.m4
Might be possible that having multiple versions of the tools
present is confusing things - I get confused too sometimes when
dealing with the auto* programs.
I suppose one thing that could be tried is manually stepping thru
autogen.sh and run the commands 'libtoolize --force --copy',
'aclocal', 'autoheader', 'automake' and finally 'autoconf'
checking at each step if the macro substitutions have happened
as expected.
Looking at the ./configure script at the lines where the errors
occur might also give a hint as to what's not right.
The key problem seems to be that autoconf and automake aren't
finding a couple very basic macros - quite puzzling.
Steven Schultz
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
