[Dovecot] autogen.sh fails -> "required file `./config.rpath' not found"
if i run
autogen.shon fresh 1.1.beta9 source, it fails @
./autogen.sh
...
100%[====================================>] 154,427 115.09K/s
08:45:56 (114.82 KB/s) - `wiki-export.tar.gz' saved [154427/154427]
configure.in:16: required file `./config.rpath' not found
configure.in:5: installing `./missing'
configure.in:5: installing `./install-sh'
src/auth/Makefile.am: installing `./depcomp'
autoreconf: automake failed with exit status: 1per advice,
"gettext-related test failures: config.rpath presence"
http://www.mail-archive.com/automake-patches@gnu.org/msg00426.htmla simple
touch config.rpath
./autogen.shfixes the problem.
hth
On 2007-11-28 08:47:14 -0800, snowcrash wrote:
on fresh 1.1.beta9 source, it fails @
./autogen.sh ... 100%[====================================>] 154,427 115.09K/s 08:45:56 (114.82 KB/s) -
wiki-export.tar.gz' saved [154427/154427] configure.in:16: required file./config.rpath' not found configure.in:5: installing./missing' configure.in:5: installing./install-sh' src/auth/Makefile.am: installing `./depcomp' autoreconf: automake failed with exit status: 1per advice,
"gettext-related test failures: config.rpath presence" http://www.mail-archive.com/automake-patches@gnu.org/msg00426.html
a simple
touch config.rpath ./autogen.sh
fixes the problem.
the real solution would be to copy the config.rpath [1] from your distro into the source dir. this requires the gettext devel files to be installed.
now the question is when using the 1.1b9 tarball. why do you run autogen.sh at all?
darix[1] /usr/share/gettext/config.rpath on my distro
-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
the real solution would be to copy the config.rpath [1] from your distro into the source dir. this requires the gettext devel files to be installed.
i'm not using nls/gettext. afaict, it's not even mentioned (in configure, doc, INSTALL, etc) as an option. then, gettext shouldn't be a requirement (even though it's installed on my system ...).
the point is, the check for the file is there, but the file is not included. autogen.sh *would* copy it if i spec'd the location of my gettext in /usr/local/share (odd that the check wouldn't be for 'standard' locations ... ), but, again, why's it asked for?
now the question is when using the 1.1b9 tarball. why do you run autogen.sh at all?
i'm not using the tarball -- rather
hg clone -r1.1.beta9 http://hg.dovecot.org/dovecot
instructions, of course, are:
"If you got Dovecot from Mercurial, for instance with
---%<------------------------------------------------------------------------- hg clone http://hg.dovecot.org/dovecot/ ---%<-------------------------------------------------------------------------
you will first need to run './autogen.sh' to generate the 'configure' script and some other files."
On 2007-11-28 10:29:26 -0800, snowcrash wrote:
the real solution would be to copy the config.rpath [1] from your distro into the source dir. this requires the gettext devel files to be installed.
i'm not using nls/gettext. afaict, it's not even mentioned (in configure, doc, INSTALL, etc) as an option. then, gettext shouldn't be a requirement (even though it's installed on my system ...).
the point is, the check for the file is there, but the file is not included. autogen.sh *would* copy it if i spec'd the location of my gettext in /usr/local/share (odd that the check wouldn't be for 'standard' locations ... ), but, again, why's it asked for?
now the question is when using the 1.1b9 tarball. why do you run autogen.sh at all?
i'm not using the tarball -- rather
hg clone -r1.1.beta9 http://hg.dovecot.org/dovecot
instructions, of course, are:
"If you got Dovecot from Mercurial, for instance with
---%<------------------------------------------------------------------------- hg clone http://hg.dovecot.org/dovecot/ ---%<-------------------------------------------------------------------------
you will first need to run './autogen.sh' to generate the 'configure' script and some other files."
it wasnt me who brought that shit into the autotools. but i would not hackaround with empty files in that area.
just my 2 cents,
darix-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
fair nuf. my point simply is, the check should make sense --- or at least be documented. and the email was just an fyi.
personally, i can work around it ...
cheers.
participants (2)
-
Marcus Rueckert
-
snowcrash