[opensuse-gnome] Gnome build system problems
Hi all I'm trying to build NetworkManager from SVN on factory. I can't get autogen.sh to complete. I've installed gnome-common, automake, autoconf, libtool, intltool, pkg-config, gettext-runtime and gettext-tools, and still get the following error: (http://www.pastebin.ca/924656) wstephenson@gorse:/home/wstephenson/code/kde/networkmgr/NetworkManager-svn/NetworkManager-0.7.0> ./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.7... testing automake-1.10... found 1.10.1 checking for libtool >= 1.4.3... testing libtoolize... found 1.5.26 checking for glib-gettext >= 2.2.0... testing glib-gettextize... found 2.15.5 checking for intltool >= 0.25... testing intltoolize... found 0.35.5 checking for pkg-config >= 0.14.0... testing pkg-config... found 0.23 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 ./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... intltoolize: 'po/Makefile.in.in' is out of date: use '--force' to overwrite I understand that most of the requests and suggestions in the output above are normally ignored - I get similar output when building on 10.3 successfully. I get the same result if autogen.sh is run with the args to configure. captain_magnus tried the same, with the gnome-devel pattern installed, and got the same result. Who knows the gnome buildsystem well enough to say what's missing here? TIA Will -- Will Stephenson Desktop Engineer KDE Team -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Saturday 01 March 2008 23:34:06 Will Stephenson wrote:
I'm trying to build NetworkManager from SVN on factory. I can't get autogen.sh to complete. I've installed gnome-common, automake, autoconf, libtool, intltool, pkg-config, gettext-runtime and gettext-tools, and still get the following error:
I've gone back to 10.3 and can't build SVN trunk there either now, so I assume the change was in NM itself. Tambet, what steps do you take to turn the NM source tree into a tarball for packaging? Are there new build dependencies I don't know about? I'm no wiser from reading the output of autogen.sh. The reason I want to update is that our current Factory NM packages are returning invalid introspection XML eg <property/>...</property>, but the FC9 ones are not. Will -- Desktop Engineer KDE Team -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Sunday 02 March 2008 10:07:56 Will Stephenson wrote:
I've gone back to 10.3 and can't build SVN trunk there either now, so I assume the change was in NM itself.
Now I'm really unsure. I looked at gnome-autogen.sh and saw that the failure comes from intltoolize - the error message intltoolize: 'po/Makefile.in.in' is out of date: use '--force' to overwrite is wrong as gnome-autogen.sh calls intltoolize with --force, copying intltool's own /usr/share/intltool/Makefile.in.in into the project. So intltool seems to be inconsistent with itself, the "grep INTLTOOL_MAKEFILE" on its own copy of that file at the end of intltoolize fails. Is it worth updating intltool to the latest 0.37? Will -- Desktop Engineer KDE Team -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
It was a local problem: I found another copy of the NetworkManager source tree inside the sources I was trying to bootstrap (NetworkManager-0.7.0/NetworkManager-0.7.0), oops, and a find in gnome-autogen.sh was finding its configure.* files in the wrong place and confusing intltoolize. Sorry for the noise! Will -- Desktop Engineer KDE Team -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Sun, 2008-03-02 at 14:54 +0100, Will Stephenson wrote:
It was a local problem: I found another copy of the NetworkManager source tree inside the sources I was trying to bootstrap (NetworkManager-0.7.0/NetworkManager-0.7.0), oops, and a find in gnome-autogen.sh was finding its configure.* files in the wrong place and confusing intltoolize.
FWIW, I believe it does this because autoconf also autodetects subdirs
with configure.* scripts.
-JP
--
JP Rosevear
-- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Tue, 2008-03-04 at 11:14 -0500, JP Rosevear wrote:
On Sun, 2008-03-02 at 14:54 +0100, Will Stephenson wrote:
It was a local problem: I found another copy of the NetworkManager source tree inside the sources I was trying to bootstrap (NetworkManager-0.7.0/NetworkManager-0.7.0), oops, and a find in gnome-autogen.sh was finding its configure.* files in the wrong place and confusing intltoolize.
FWIW, I believe it does this because autoconf also autodetects subdirs with configure.* scripts.
It is actually gnome-autogen.sh that does that. You can avoid it by putting in the same directory as the offending configure.{in,ac} an empty file named NO-AUTO-GEN In that case, gnome-autogen will ignore it. Hub -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
I see you already resolved your problem, but: On Sun, 2008-03-02 at 13:22 +0100, Will Stephenson wrote: [...]
Now I'm really unsure. I looked at gnome-autogen.sh and saw that the failure comes from intltoolize - the error message
intltoolize: 'po/Makefile.in.in' is out of date: use '--force' to overwrite
is wrong as gnome-autogen.sh calls intltoolize with --force, copying intltool's own /usr/share/intltool/Makefile.in.in into the project. So intltool seems to be inconsistent with itself, the "grep INTLTOOL_MAKEFILE" on its own copy of that file at the end of intltoolize fails.
Is it worth updating intltool to the latest 0.37?
Yes, probably. Some version between 0.35.5 and 0.37.1 broke lots of things when we were working on 10.3. I just submitted 0.37.1 to BETA and will move it into STABLE/Factory once I'm sure it doesn't break everything. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Mon, 2008-03-03 at 18:50 -0600, Michael Wolf wrote:
I just submitted 0.37.1 to BETA and will move it into STABLE/Factory once I'm sure it doesn't break everything.
It breaks lots of packages, just like last time. I'll try to look into it further soon. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Wed, 2008-03-05 at 10:22 -0600, Michael Wolf wrote:
On Mon, 2008-03-03 at 18:50 -0600, Michael Wolf wrote:
I just submitted 0.37.1 to BETA and will move it into STABLE/Factory once I'm sure it doesn't break everything.
It breaks lots of packages, just like last time. I'll try to look into it further soon.
So, the problem happens when a) you run autoreconf, and b) the tarball was disted with a different version of intltool. The solution is to run libtoolize --force after autoreconf. I've made this change for a number of packages. Some of the autoreconf calls in the failing packages were unnecessary, however. I've removed most of the unnecessary calls. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Sun, Mar 2, 2008 at 3:07 AM, Will Stephenson
Tambet, what steps do you take to turn the NM source tree into a tarball for packaging? Are there new build dependencies I don't know about? I'm no wiser from reading the output of autogen.sh.
Must be something wrong with your toolset, all I need to do is the regular 'autogen.sh; make dist'
The reason I want to update is that our current Factory NM packages are returning invalid introspection XML eg <property/>...</property>, but the FC9 ones are not.
Why do you ask on mailing lists if you don't believe the answer? It is a bug in dbus-glib, it's fixed, and it's in factory. Upgrade your dbus-glib package. The NM packages in the factory are from Friday evening, so you're just wasting your time. Tambet -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Tuesday 04 March 2008 05:51:48 Tambet Ingo wrote:
Why do you ask on mailing lists if you don't believe the answer? It is a bug in dbus-glib, it's fixed, and it's in factory. Upgrade your dbus-glib package. The NM packages in the factory are from Friday evening, so you're just wasting your time.
Offside! Gnome list build system problem mails: Sat night/Sun morning NM list introspection xml mail: Sun evening -- Will Stephenson Desktop Engineer KDE Team -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
participants (5)
-
Hubert Figuiere -
JP Rosevear -
Michael Wolf -
Tambet Ingo -
Will Stephenson