After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 476726 - autogen.sh failing
autogen.sh failing
Status: RESOLVED WONTFIX
Product: vte
Classification: Core
Component: general
0.16.x
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-13 21:41 UTC by Pascal Terjan
Modified: 2008-11-24 18:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
Define AC_CONFIG_AUX_DIR to . (384 bytes, patch)
2007-09-13 21:43 UTC, Pascal Terjan
rejected Details | Review

Description Pascal Terjan 2007-09-13 21:41:58 UTC
[pterjan@plop vte2]$ LC_ALL=C ./autogen.sh 
/usr/bin/gnome-autogen.sh
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.61
checking for automake >= 1.8...
  testing automake-1.10... found 1.10
checking for libtool >= 1.4.3...
  testing libtoolize... found 1.5.22
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.14.0
checking for intltool >= 0.25...
  testing intltoolize... found 0.36.1
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 0.21
checking for gtk-doc >= 1.0...
  testing gtkdocize... found 1.8
checking for gnome-common >= 2.3.0...
  testing gnome-doc-common... found 2.18.0
Checking for required M4 macros...
Checking for forbidden M4 macros...
**Warning**: 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.

Processing ./gnome-pty-helper/configure.in
Running gnome-doc-common...
Running aclocal-1.10...
Running autoconf...
Running autoheader...
Running automake-1.10...
Processing ./configure.in
Running libtoolize...
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `../..'.
Running glib-gettextize... Ignore non-fatal messages.
Copying file mkinstalldirs
Copying file po/Makefile.in.in

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

Running intltoolize...
cp: cannot create regular file `po/Makefile.in.in': No such file or directory
intltoolize: cannot copy '/usr/share/intltool/Makefile.in.in' to 'po/Makefile.in.in'
Comment 1 Pascal Terjan 2007-09-13 21:42:42 UTC
It is actually trying to create the file as ../../po/Makefile.in.in and fails because ../../po does not exist
Comment 2 Pascal Terjan 2007-09-13 21:43:44 UTC
Created attachment 95552 [details] [review]
Define AC_CONFIG_AUX_DIR to .

Here is a patch making it work for me, don't know if this is the correct fix
Comment 3 Behdad Esfahbod 2007-09-13 23:04:34 UTC
Doesn't make sense to me.
Comment 4 Pascal Terjan 2007-09-14 06:35:02 UTC
OK, I have tried to understand better what happened.

     If `AC_CONFIG_AUX_DIR' is not given, the scripts are looked for in
     their standard locations.  For `mdate-sh', `texinfo.tex', and
     `ylwrap', the standard location is the source directory
     corresponding to the current `Makefile.am'.  For the rest, the
     standard location is the first one of `.', `..', or `../..'
     (relative to the top source directory) that provides any one of
     the helper scripts.  *Note Finding `configure' Input:
     (autoconf)Input.


So, if one of the scripts (install-sh, libtool, ...) does not exist in the current directory it will look into .. and ../.. and then will work in that directory.

In my case ../.. was my home. I found that it had polluted my home with ltmain.sh, config.guess and config.sub (maybe others that I did not notice).

I don't know why did it decide to use it, maybe because it contains an install.sh as I read that autotools used to have a install.sh in the past.

Setting it to . will make it get the scripts that are missing from the system instead of looking for them in ".." and "../..". 
Comment 6 vivek 2007-09-14 08:44:30 UTC
Pascal terjan,
The change was made with the same understanding as in your comment #4.
As libtoolize was looking into the wrong directory - in this case "../..".
man libtoolize :
"If ‘libtoolize’ detects an explicit call to ‘AC_CONFIG_AUX_DIR’ in your ‘configure.in’, it will put the files in the specified directory."

And the change seems to be working without any problems till now.
Comment 7 Behdad Esfahbod 2007-09-14 19:56:31 UTC
In that case all libraries should be needing this.  Is that what you are implying?  In that case can you bring up on desktop-devel-list?
Comment 8 Pascal Terjan 2007-09-14 20:07:51 UTC
Yes it looks like it is needed everywhere, I'll post on the list.
Comment 9 Christian Persch 2007-09-14 23:26:47 UTC
Which distro and auto* versions is that with? I cannot repro this on gutsy.
Comment 10 Pascal Terjan 2007-09-15 05:52:08 UTC
I'm using Mandriva Cooker with autoconf 2.61 and automake 1.10

I tried "mv ../../install.sh ../../my-install.sh" and it avoids the problem, so I think I was right on my explanation
Comment 11 Pascal Terjan 2008-10-19 23:54:30 UTC
This bug is still present (but yes, it needs to be fixed in a lot of places)

====
mkdir -p t/t
cd t
touch install.sh
cd t
svn co svn+ssh://svn.gnome.org/svn/vte/trunk vte
cd vte
./autogen.sh
====

It will break with:

configure.in:38: required file `./ltmain.sh' not found

And ../.. will be polluted:

[pterjan@plop vte]$ ls ../../           
config.guess*  config.sub*  install.sh  ltmain.sh  t/
Comment 12 Behdad Esfahbod 2008-10-20 04:40:00 UTC
Before we change all packages, can you report this to bug-libtool@gnu.org please?  CC me also.  Thanks.
Comment 13 Behdad Esfahbod 2008-11-24 18:50:06 UTC
I don't think any fix for this is needed in vte.  Any fix should be done in libtool itself.