Re: new build order



Bastien Nocera wrote:

On Fri, 2001-10-26 at 20:25, George wrote:

On Wed, Oct 24, 2001 at 11:36:46PM +0100, Bastien Nocera wrote:

We talked about that on the mailing-list. (See my crummy patches a
little while earlier)

Phlip, just switch automake 1.5 for an automake 1.4 in the bootstrap
phase of the vicious-build-scripts. I didn't change it because I didn't
have time to test. Tell us how your platform compilation goes using a
1.4 version, and I'll update the scripts then.

Dudes, if you find stuff liek that just edit vbs.  I updated to automake 1.5
cuz I thought ... yay a new version ... and didn't realize it had so many
issues.  I'm not on a computer where I can change cvs ... can you switch it for
1.4 for now?  thanks.

I keep forgetting about this when I'm on my computer.


Done, I switched it to automake 1.4p5. We shouldn't have any build
problems of this kind anymore.

Cheers



Well, I get up to gtk+ now, at which point I get this error:


creating gdk-pixbuf-scan

lt-gdk-pixbuf-scan (pid:2021): GRuntime-CRITICAL **: gtype.c:1824:g_type_register_static(): initialization assertion failed, use g_type_init() prior to this function

lt-gdk-pixbuf-scan (pid:2021): GRuntime-CRITICAL **: gtype.c:1824:g_type_register_static(): initialization assertion failed, use g_type_init() prior to this function

lt-gdk-pixbuf-scan (pid:2021): GRuntime-WARNING **: invalid cast from (NULL) pointer to `<invalid>'
Scan failed
make[4]: *** [scan-build.stamp] Error 255
make[4]: Leaving directory `/gnome/head/cvs/gtk+/docs/reference/gdk-pixbuf'

If I --disable-gtk-doc, GTK+ builds and installs, but running any of the tests gives me a similar error (about g_type_init()).


Julian
--
email: julian jabber org
jabber:julian jabber org




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]