Le 07/05/2012 18:00, Ken Moffat a écrit : > In my case I build dbus, cairo, gtk-doc, dbus-glib, ..., > gobject-introspection in that order, followed by pango, atk, > shared-mime-info, cups, gdk-pixbuf, gtk2, gtk3. I don't imagine that > variations in the build order are causing this, but librsvg is > building fine for me. I don't have vala, and when I used to build it > it was near the end of my build. I remember someone had a problem in > babl or gegl that was attributed to using vapigen, and I know Andy has > reported problems in current libgsf that I don't get, so I'd better > ask if you guys have vala installed ? ĸen Well, I had vala installed. But so did Armin, I think, and for him, it compiles OK.
Couldn't it be that building g-i before cairo or g-i after cairo does not generate exactly the same configuration? Since I use some automation, and g-i is marked optional (required to build gnome), which is hard to detect with automation, last time, I built g-i as almost the first package (maybe after D-Bus). Today, I am trying the other way around, which seems to be the order you used. I'll let you know whether librsvg compiles without the sed. But before that, I need to address the xulrunner test I promised to Andy (unfortunately, I have other unrelated things to do too). Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
