[Plib-devel] errors when compiling plib: autogen.sh problems with automake 1.8.0
Brought to you by:
sjbaker
From: Oliver C. <kre...@gm...> - 2004-07-24 00:14:15
|
Hello, i upgraded my linux distribution to Slackware 10.0 that ships with automake version 1.8.0 and tried to compile the cvs version of plib but i get the following errors after running ./autogen.sh ************************************************************ $ ./autogen.sh Running aclocal /usr/share/aclocal/xmms.m4:17: warning: underquoted definition of XMMS_TEST_VERSION run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending%20aclocal /usr/share/aclocal/xmms.m4:62: warning: underquoted definition of AM_PATH_XMMS /usr/share/aclocal/vorbis.m4:9: warning: underquoted definition of XIPH_PATH_VORBIS /usr/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES /usr/share/aclocal/pilot-link.m4:1: warning: underquoted definition of AC_PILOT_LINK_HOOK /usr/share/aclocal/ogg.m4:8: warning: underquoted definition of XIPH_PATH_OGG /usr/share/aclocal/nspr.m4:8: warning: underquoted definition of AM_PATH_NSPR /usr/share/aclocal/libmikmod.m4:11: warning: underquoted definition of AM_PATH_LIBMIKMOD /usr/share/aclocal/libOggFLAC.m4:7: warning: underquoted definition of AM_PATH_LIBOGGFLAC /usr/share/aclocal/libOggFLAC++.m4:8: warning: underquoted definition of AM_PATH_LIBOGGFLACPP /usr/share/aclocal/libIDL.m4:6: warning: underquoted definition of AM_PATH_LIBIDL /usr/share/aclocal/libFLAC.m4:7: warning: underquoted definition of AM_PATH_LIBFLAC /usr/share/aclocal/libFLAC++.m4:8: warning: underquoted definition of AM_PATH_LIBFLACPP /usr/share/aclocal/imlib.m4:9: warning: underquoted definition of AM_PATH_IMLIB /usr/share/aclocal/imlib.m4:167: warning: underquoted definition of AM_PATH_GDK_IMLIB /usr/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK /usr/share/aclocal/gnet-2.0.m4:8: warning: underquoted definition of AM_PATH_GNET_2_0 /usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB /usr/share/aclocal/gimpprint.m4:8: warning: underquoted definition of AM_PATH_GIMPPRINT /usr/share/aclocal/gdk-pixbuf.m4:12: warning: underquoted definition of AM_PATH_GDK_PIXBUF /usr/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE /usr/share/aclocal/ao.m4:9: warning: underquoted definition of XIPH_PATH_AO /usr/share/aclocal/ac_find_motif.m4:21: warning: underquoted definition of AC_FIND_MOTIF /usr/share/aclocal/ac_find_motif.m4:223: warning: underquoted definition of AC_FIND_LIBXP /usr/share/aclocal/aalib.m4:12: warning: underquoted definition of AM_PATH_AALIB /usr/share/aclocal/ORBit.m4:4: warning: underquoted definition of AM_PATH_ORBIT Can't locate object method "path" via package "Request" at /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 94. aclocal: autom4te failed with exit status: 1 Running automake Can't locate object method "path" via package "Request" at /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 94. automake: autoconf failed with exit status: 1 Running autoconf Can't locate object method "path" via package "Request" at /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 94. ====================================== Now you are ready to run './configure' ====================================== $./configure configure: error: cannot find install-sh or install.sh in . ./.. ./../.. $ ************************************************************ So there seems to be a problem with plib's macro definitions and the stricter behavior of automake version 1.8.0. Just read this: ************************************************************* Writing your own aclocal macros =============================== The `aclocal' program doesn't have any built-in knowledge of any macros, so it is easy to extend it with your own macros. This can be used by libraries which want to supply their own Autoconf macros for use by other programs. For instance the `gettext' library supplies a macro `AM_GNU_GETTEXT' which should be used by any package using `gettext'. When the library is installed, it installs this macro so that `aclocal' will find it. A macro file's name should end in `.m4'. Such files should be installed in `$(datadir)/aclocal'. This is as simple as writing: aclocaldir = $(datadir)/aclocal aclocal_DATA = mymacro.m4 myothermacro.m4 A file of macros should be a series of properly quoted `AC_DEFUN''s (*note Macro Definitions: (autoconf)Macro Definitions.). The `aclocal' programs also understands `AC_REQUIRE' (*note Prerequisite Macros: (autoconf)Prerequisite Macros.), so it is safe to put each macro in a separate file. Each file should have no side effects but macro definitions. Especially, any call to `AC_PREREQ' should be done inside the defined macro, not at the beginning of the file. Starting with Automake 1.8, `aclocal' will warn about all underquoted calls to `AC_DEFUN'. We realize this will annoy a lot of people, because `aclocal' was not so strict in the past and many third party macros are underquoted; and we have to apologize for this temporary inconvenience. The reason we have to be stricter is that a future implementation of `aclocal' (*note Future of aclocal::) will have to temporary include all these third party `.m4' files, maybe several times, even those which are not actually needed. Doing so should alleviate many problem of the current implementation, however it requires a stricter style from the macro authors. Hopefully it is easy to revise the existing macros. For instance # bad style AC_PREREQ(2.57) AC_DEFUN(AX_FOOBAR, [AC_REQUIRE([AX_SOMETHING])dnl AX_FOO AX_BAR ]) should be rewritten as AC_DEFUN([AX_FOOBAR], [AC_PREREQ(2.57)dnl AC_REQUIRE([AX_SOMETHING])dnl AX_FOO AX_BAR ]) Wrapping the `AC_PREREQ' call inside the macro ensures that Autoconf 2.57 will not be required if `AX_FOOBAR' is not actually used. Most importantly, quoting the first argument of `AC_DEFUN' allows the macro to be redefined or included twice (otherwise this first argument would be expansed during the second definition). If you have been directed here by the `aclocal' diagnostic but are not the maintainer of the implicated macro, you will want to contact the maintainer of that macro. Please make sure you have the last version of the macro and that the problem already hasn't been reported before doing so: people tend to work faster when they aren't flooded by mails. Another situation where `aclocal' is commonly used is to manage macros which are used locally by the package, *Note Local Macros::. ************************************************************* And read this: http://sources.redhat.com/automake/automake.html#Extending%20aclocal Can someone fix these macro definitions shipped with plib's cvs version? Best Regards, Oliver C. |