Re: gEDA-dev: gschem's mkinstalldirs problem

[Dan McMahill <dan-at-NOSPAMmcmahill_dot_net>]

Stuart Brorson wrote:


I don't know the solution to this specific problem, but I can say
> this:  On my older FC1 machine I often have problems building gEDA
> from CVS since AM_GNU_GETTEXT is not defined anywhere on my M4 search
> path.   I'm not an expert, so I don't know why this is.  What I
> generally end up doing is locating the relevant .m4 file, and then
> setting the env variable ACLOCAL_FLAGS to point to the file's
> directory.  [1]
> 
> It's possible part of the problem is that AM_GNU_TEXTTEXT is defined
> in the /usr/local/ hierarchy, whereas Fedora and RedHat tend to assume
> things are located in the /usr hierarchy.
> 
> My suggestion therefore is to beef up and make more robust the stuff
> in configure.ac which searches out the GNU gettext M4 stuff.
> 
> Just a thought . . . .
> 
> Stuart

What you describe doesn't sound like a configure.ac problem.  It is a 
problem that when you run aclocal which creates ./aclocal.m4 that 
aclocal doesn't know every place where you may have .m4 files installed. 
  Once you run aclocal, then all of the extra macros (like the 
pkg-config ones, gettext ones, etc) will be in your aclocal.m4 file.

It could also be that the wrong 'autopoint' (part of gettext) is in your 
path.


-Dan



_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev