Re: New autogen.sh

[Martin Baulig <martin home-of-linux org>]

On Mon, 7 Dec 1998, Junichi Saito wrote:

> Probably is this due to the use of gettext 0.10.35 instead of 'intl'. I
> now get the following messages while configuring certain modules such as
> gnome-libs, gnome-core, .etc :
> 
> Running gettextize...  Ignore non-fatal messages.  
> sed: can't read aclocal.m4: No such file or directory 
> You should update your own `aclocal.m4' by adding the necessary macro
> packages gettext.m4, lcmessage.m4 and progtest.m4 from the directory
> `/aclocal' 
> Making./aclocal.m4 writable ...  
> chmod: ./aclocal.m4: No such file or directory

Just changed this so it will make sure this file exists before doing
the chmod on it.

The problem here was that the new gettextize normally makes aclocal.m4
symbolic link to /usr/share/... where normal people won't have write
access to. If you change this to use this --copy parameter it will create
a file aclocal.m4 and not make it a symlink, but this file will have mode
0444 (readable by everyone but not writable by anybody) so the next 
aclocal will fail. So it was necessary to do the chmod.

Another problem is that it seems gettextize doesn't like it very much
if aclocal.m4 does not exist (that's when you run autogen.sh the first
time).

Perhaps we should change this to run aclocal first and then gettextize.

> 
> Are these non-fatal messages previously referred to, thus not important?
> 
> It seems I get them because I compile in directories different from those
> where the sources are and that 'autogen.sh' presuppose now a build was
> previously made in the source directories, as aclocal.m4 is a generated

No, it works with builddir != srcdir - I tried that out ...

Martin

-----------------------------------------------------------------
   Martin Baulig - Angewandte Mathematik - Universitaet Trier
   martin@home-of-linux.org, http://www.home-of-linux.org/
------------------------------------------------------------------