[gnome-love] Re: autoconf macro issues
- From: Christian Kirbach <Christian KIrbach student uni-siegen de>
- To: gnome-love gnome org
- Subject: [gnome-love] Re: autoconf macro issues
- Date: Wed, 08 Jun 2005 11:50:14 +0200
Am Dienstag, den 07.06.2005, 12:39 +0200 schrieb BJörn Lindqvist:
I think you are missing gnome-common which contain gnome-autogen.sh
and gtk-doc which unsurprisingly has gtk-doc.m4. Then all m4 scripts
No, I wasn't missing gnome-common
Note that it is not really needed to build the whole gnome yourself to
start hacking. Most modules from CVS will happily compile with older,
stable releases of their dependancies.
Sure, but the problem even occured when doing a 'jhbuild buildone foo'
Now, even jhbuild bootstrap did not make any change, but a
export ACLOCAL_FLAGS="-I /opt/gnome2/share/aclocal"
did get me past, but just to get stuck a few line later...
=========================
Please add the files
codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
progtest.m4
from the /opt/gnome2/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...
Running aclocal-1.4...
Running autoconf2.50...
Running autoheader2.50...
Running automake-1.4...
aclocal.m4: 1901: `jm_MAINTAINER_MODE' is obsolete; use
`AM_MAINTAINER_MODE'
*** error during stage configure of gnomeicu: could not configure module
*** [1/1]
=================
And yes, I have copied the listed m4 macros
to /usr/share/autoconf/autoconf as asked, but that did not remedy. Also
removing aclocal.m4 did not help either.
C'mon, I have spend hours now ...
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]