On Tue, 2004-12-14 at 15:28 +0100, Egon Andersen wrote:
Hi,
I've experienced problems with g_strdup_printf() in glib 2.4.8 when I
try to print 64-bit integers on Windows.
I have the following line in my code:
intmax_t se_nr; /* ISO-C99 */
...
se_nr = ... /* e.g. 12345678 */
...
Hi,
Olexiy Avramchenko [EMAIL PROTECTED] writes:
So perhaps the 2.4.8 on the gtk.org site is bad? (thats where I got it from).
The one line from http://www.gtk.org :
# Version 2.4.9 of the GTK+ widget toolkit is now available. This is a
respin of 2.4.8 which fixes a library versioning
Need help on this error,
I had no problem with other versions of Linux before. I recently
switched to Gentoo. Of course needless to say all the ebuilds installed are
newest versions as of now including glib, mesa, gtk+ etcI didnt have
any compile problem with my application. Now I get the
Mario Motta wrote:
hi all,
someone can tell me why this piece of sw compile and works even if it
should not ?
$ gcc --version
gcc (GCC) 3.3.1 (mingw special 20030804-1)
$ gcc impossible.c -o impossible
==
#include stdio.h
int main(int argc,
William Lahti wrote:
I've found a lot of posts about not being able to compile pango
because of undefined symbols from glib which people continually say is
because of an old version. I had no old version and installed Glib
2.4.8 and it had that problem. nm showed no signs of the culprit
symbols in
Owen Taylor wrote:
On Tue, 2004-12-14 at 15:28 +0100, Egon Andersen wrote:
Hi,
I've experienced problems with g_strdup_printf() in glib 2.4.8 when I
try to print 64-bit integers on Windows.
I have the following line in my code:
intmax_t se_nr; /* ISO-C99 */
...
se_nr = ... /* e.g. 12345678 */
