[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gtk-devel
Subject:    Re: Gobject-Introspection and CMPH
From:       Colin Walters <walters () verbum ! org>
Date:       2010-12-16 19:58:57
Message-ID: AANLkTi=J79Uy+CrJs=6tF61Vs4S32B1aW-tbaEP0mE6P () mail ! gmail ! com
[Download RAW message or body]

On Thu, Dec 16, 2010 at 2:30 PM, John Ralls <jralls@ceridwen.us> wrote:
> 
> On Dec 16, 2010, at 9:47 AM, Colin Walters wrote:
> 
> > On Wed, Dec 15, 2010 at 8:43 PM, John Ralls <jralls@ceridwen.us> wrote:
> > 
> > Okay well, I *think* you answered my question, which is that you want
> > the stack to build with "c99".
> 
> No, but Emmanuele did: It should be c89. Gobject-introsopection has been failing \
> that for some time, but before you added cmph, it built with c99.

Okay, someone tell me how exactly you're building glib with c89, on
what operating system.  It fails for me here on RHEL6 (gcc (GCC) 4.4.4
20100726 (Red Hat 4.4.4-13)), if I specify -std=c89 in CFLAGS:

http://people.gnome.org/~walters/build-glib-c89.log

It looks to me like we also need to specify at least _POSIX_SOURCE
defined, but even that's not good enough because we need va_copy,
which requires -D_GNU_SOURCE.   Hmm, actually doing this breaks half
the configure checks if we just specify it on "make" invocation,
because we find "va_copy" during detection since we're using the
default gnu89.

If I manually run configure like:
./configure --prefix=/src/build/jhbuild
--libdir=/src/build/jhbuild/lib64 CFLAGS='-Wall -std=c89'

then it errors out later trying to find arpa/nameser_compat.h.

So...if people are claiming this really works, let me know how you're
doing it...
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list


[prev in list] [next in list] [prev in thread] [next in thread]