On Fri, Sep 27, 2002 at 12:34:04AM +0200, Grzegorz Adam Hankiewicz wrote: > Hi. > > No problem, I installed the source version and now autogen.sh continues, > but drops lot's of warnings: > > 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. > WARNING: aclocal's directory is /usr/local/share/aclocal, but... > no file /usr/local/share/aclocal/glib-2.0.m4 > You may see fatal macro warnings below. > If these files are installed in /some/dir, set the ACLOCAL_FLAGS > environment variable to "-I /some/dir", or install > /usr/local/share/aclocal/glib-2.0.m4. > > WARNING: aclocal's directory is /usr/local/share/aclocal, but... > no file /usr/local/share/aclocal/gtk-2.0.m4 > ...blah blah blah... > > Now, I have these files, but they are installed in another place: > > [gregorio:37] [~/cvs/libs/pygtk]$ locate glib-2.0.m4 > /usr/share/aclocal/glib-2.0.m4 > [gregorio:38] [~/cvs/libs/pygtk]$ locate gtk-2.0.m4 > /usr/share/aclocal/gtk-2.0.m4 > [gregorio:39] [~/cvs/libs/pygtk]$ locate gettext.m4 > /home/gregorio/instalacion_manual/mutt-1.4/m4/gettext.m4 > /mnt/g/cvs/progs/source-navigator-support/gettext.m4 > /usr/share/aclocal/gettext.m4 > /usr/share/aclocal/glib-gettext.m4 > > So, looks like automake is looking for the .m4 files only in the > /usr/local/share/aclocal/, when all the packages are in another place. I > expected to force automake look there, but without success: the strange > info manual doesn't seem to tell anything about path configuration (unless > it's about where to put installed files by the generated makefiles). > > I guess I will have to make some symlinks, but before I do so, does > somebody know if there's a way to tell automake where to look for > .m4 files?
If you have a relatively new automake/aclocal, the easiest way to tell aclocal to look in the /usr/share/aclocal directory is to create a file called "dirlist" in the /usr/local/share/aclocal directory, and the file should have the line /usr/share/aclocal When aclocal is run, it will see this file and append '/usr/share/aclocal' to the directories it searches for .m4 files for making macros. There's more info about this in the automake info pages in the 'Macro search path' page. I just added a dirlist file to the /usr/local/share/aclocal directory to handle just the sort of thing you're dealing with, and things have worked smoothly with it there. Good luck with pygtk-2.0. Art Haas -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin, Historical Review of Pennsylvania, 1759 _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
