From: Paul K. <pau...@xs...> - 2005-05-12 21:06:26
|
Hi Michael, I still think there is something wrong with the configuration files. Here is what I do: - clean get from cvs - ./configure tux lcd4linux # make cd . && aclocal-1.4 aclocal: macro `AM_PATH_PYTHON' required but not defined make: *** [aclocal.m4] Error 1 This definition is cached in aclocal.m4 and is in I have to throw away Makefile, Makefile.in and aclocal.m4 and do ./bootstrap ./configure To recreate the previous files. The do make to start the build process. make But no object files are created and the linking stage fails See the attached files for the make output. I have no idea what goes wrong here :'( bye, Paul Michael Reinelt wrote: >Hi Paul, > > > >>Ok, I think I know what the problems is. But I am not sure on how to >>solve it. >>For some reason the python.m4 in the local directory is not found by >>aclocal. >>If I run >> >>aclocal -I . >> >>to specify the local directory as an include directory, followed by >>make, it works fine. >> >>So there are several possible causes of this different behaviour. >> >>1) >>you run a different version of aclocal. I use aclocal 1.4 but I noticed >>that version 1.9 has the python.m4 in its standard macro set. (I still >>can't figure out how gentoo selects different version of aclocal to use) >> >>2) >>for some reason you have the local directory included in the aclocal >>include path by default. >> >> > >I don't think that you have to include . in the search path. If this >would be necessary, aclocal would not find drivers.m4, curses.m4 neither. > >But I've another strong suspicion: aclocal loads the global python.m4 >before the local one (as you said, aclocal-1.9 provides a python.m4). > >You could try to rename the python.m4 and change the reference in.. in.. >wherever it's referenced. > > >bye, Michael > > > |