From: Per-Karsten N. <pe...@ma...> - 2001-08-07 10:01:54
|
[Christian Kreibich] wrote: > I don't know about the etcher one, but the macro for these two is in > acsite.m4 for both modules, e17/apps/e/acsite.m4, > e17/apps/efsd/acsite.m4. According to my autoconf manual, aclocal.m4 and > acsite.m4 are used for generating the configure script by autoconf. > > So for some reason your autoconf doesn't see acsite.m4. I've just looked > at the manpages, and it seems that using acsite.m4 in the root directory > of the modules is not quite right: > > >From the autoconf (2.13) manpage: > > The Autoconf macros are defined in several files. Some of > the files are distributed with Autoconf; autoconf reads > them first. Then it looks for the optional file acsite.m4 > in the directory that contains the distributed Autoconf > macro files, and for the optional file aclocal.m4 in the > current directory. > > And from aclocal's: > > The contents of acinclude.m4, if it exists, are also auto > matically included in aclocal.m4. This is useful for > incorporating local macros into configure. > > So I guess it might be worth trying renaming acsite.m4 to acinclude.m4 > and leave the rest to aclocal, in case later autoconf versions are more > picky about the file locations. Anyone here who knows more about this? Thanks a lot, that actually worked like a charm. Now e, efsd and all the libs compile just fine to make pretty deb's... Etcher is still not working though, but I'll worry about that later... But, alas, e17 is still not working like it should. I put "exec /usr/bin/e17" in my .xinitrc - and all I get when it loads is a nice, black screen... If I try to click+drag across the screen, it looks like it marks stuff - but the screen output is just gobbledegook. Anyone experienced similar problems ? The apps and libs were of course built from the very latest CVS sources, of course :-) -- ask not what you can do for your country, ask what your country did to you. |