José Alburquerque wrote:
Well, I got pretty far (20/23 modules built successfully), but jhbuild gets stuck building gtkmm. The error looks like I shouldn't be getting it, but this is what it says:Jonathon Jongsma wrote:On 1/23/08, Murray Cumming <murrayc murrayc com> wrote:On Tue, 2008-01-22 at 23:18 -0500, José Alburquerque wrote:I've started using jhbuild to let it handle dependencies for me and followed the basic instructions in the manual for configuring it but each time I try to build something, it seems to be using tar balls instead of using svn. Am I doing something wrong?It uses tarballs for one or two things. Does it use svn when you do, for instance, "jhbuild buildone glibmm" ?Just to add a little more information -- anything that's not explicitly part of GNOME (i.e. an 'external dependency' such as libxml2, cairo, etc) uses tarballs. In the past, these were also checked out from the version control system, but that made jhbuild difficult to build since it was prone to build failures from development versions of external libraries. So a change was made so that only things that are actually a GNOME project should be pulled from svn.Thanks. Really appreciate this info. It clears things up a lot.
Making all in src make[3]: Entering directory `/usr/src/jhbuild-sources/gtkmm/atk/src'/opt/jhbuild-root/lib64/glibmm-2.4/proc/gmmproc -I ../../tools/m4 --defs . action . ./../atkmm No conversion from const gchar* to const Glib::ustring& defined (line: 0, parameter name: desc)
m4 failed with exit code 1. Aborting... make[3]: *** [.stamps/stamp-action] Error 1It looks like jhbuild is checking out the gtkmm-2.12 branch which is producing the error. Is there a reason that jhbuild would want to check out gtkmm-2.12 instead of the trunk? I'm using the latest jhbuild , using moduleset 'gnome-2.22' and have modules set to 'gstreamermm' (which depends on gtkmm). I'm a little confused.
-Jose