mbpurple-0.1.2 compile warnings on x86_64 arch

[GoogleCodeExporter]

What steps will reproduce the problem?
1. download mbpurple-0.1.2
2. unpack
3. `make'

What is the expected output? What do you see instead?

I expect a clean compile. I see:

$ make
cc -DPURPLE_PLUGINS -DENABLE_NLS -Wall -pthread -I. -g -O2 -pipe -fPIC
-DPIC -I/usr/include/libpurple -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include     -c -o twitter.o twitter.c
twitter.c: In function 'check_http_data':
twitter.c:266: warning: format '%d' expects type 'int', but argument 3 has
type 'gsize'
twitter.c:276: warning: format '%d' expects type 'int', but argument 3 has
type 'long int'
twitter.c:287: warning: format '%d' expects type 'int', but argument 3 has
type 'gsize'
twitter.c:287: warning: format '%d' expects type 'int', but argument 4 has
type 'gsize'
twitter.c: In function 'twitterim_send_im':
twitter.c:1071: warning: format '%d' expects type 'int', but argument 5 has
type 'long unsigned int'
twitter.c:1071: warning: format '%d' expects type 'int', but argument 5 has
type 'long unsigned int'
cc -DPURPLE_PLUGINS -DENABLE_NLS -Wall -pthread -I. -g -O2 -pipe -fPIC
-DPIC -I/usr/include/libpurple -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include     -c -o util.o util.c
cc  -shared twitter.o util.o -lpurple -lglib-2.0   -o libtwitter.so

Despite this, the proram seems to work.. it would just be nice to have a
clean compile for my architecture. :-)

What version of the product are you using? On what operating system?

I am using mbpurple-0.1.2. I am running on an x86_64 machine. I am using
gcc-4.3.2.

Please provide any additional information below.

Thanks for microblog-purple! It's quite awesome.

Original issue reported on code.google.com by jie...@gmail.com on 20 Oct 2008 at 10:01

[GoogleCodeExporter]

I think most of us are using Ubuntu on laptop. We'll fix this in the next 
release.

Original comment by somsaks on 21 Oct 2008 at 3:57

[GoogleCodeExporter]

Awesome, thanks! :)

Original comment by jie...@gmail.com on 21 Oct 2008 at 11:11

[GoogleCodeExporter]

could u try that again aginast code in trunk/ ? I found that the code is now
completely changed. Or you might wait a bit for new release.

Original comment by somsaks on 25 Oct 2008 at 5:29

[GoogleCodeExporter]

I think I 've fix this issue already. Need someone to verify.

Original comment by somsaks on 18 Mar 2009 at 2:35

• Changed state: Fixed