emacs-devel
[Top][All Lists]
Advanced

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

Re: 23.0.50; dbus


From: Michael Albinus
Subject: Re: 23.0.50; dbus
Date: Mon, 31 Dec 2007 22:43:32 +0100
User-agent: Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.50 (gnu/linux)

Peter Dyballa <address@hidden> writes:

> gcc -I/sw/include -L/sw/lib -c -DMAC_OSX  -no-cpp-precomp -I/usr/
> include/openssl -I/sw/include/pango-1.0 -I/sw/lib/freetype219/include
> -I/sw/lib/freetype219/include/freetype2 -I/sw/lib/fontconfig2/include
> -I/sw/include -I/usr/local/include -idirafter /usr/X11R6/include - 
> Demacs -DHAVE_CONFIG_H -DUSE_LUCID  -I. -I/.../emacs/src -DMAC_OSX -I/
> usr/X11R6/include -Dtemacs  -I/sw/include/glib-2.0 -I/sw/lib/glib-2.0/
> include -I/sw/include/gtk-2.0 -I/sw/include/librsvg-2 -I/sw/include/
> dbus-1.0 -I/sw/lib/dbus-1.0/include -bind_at_load -pipe -fPIC -
> mcpu=7450 -mtune=7450 -fast -mpim-altivec -ftree-vectorize -foptimize-
> register-move -freorder-blocks -freorder-blocks-and-partition -
> fthread-jumps -fpeephole -fno-crossjumping dbusbind.c
> dbusbind.c: In function ‘xd_append_arg’:
> dbusbind.c:344: warning: pointer targets in assignment differ in
> signedness
> dbusbind.c:350: warning: pointer targets in assignment differ in
> signedness
> dbusbind.c:392: warning: pointer targets in assignment differ in
> signedness

These problems shall be fixed now, too.

> dbusbind.c: In function ‘xd_read_message’:
> dbusbind.c:983: warning: pointer targets in passing argument 2 of
> strcmp’ differ in signedness
> dbusbind.c:986: warning: pointer targets in passing argument 2 of
> strcmp’ differ in signedness
> dbusbind.c: In function ‘Fdbus_register_signal’:
> dbusbind.c:1089: warning: pointer targets in passing argument 1 of
> strlen’ differ in signedness
> dbusbind.c:1090: warning: pointer targets in passing argument 1 of
> strcmp’ differ in signedness
> dbusbind.c:1091: warning: pointer targets in passing argument 1 of
> strncmp’ differ in signedness
> dbusbind.c:1104: warning: pointer targets in passing argument 1 of
> strlen’ differ in signedness

Here I'm lost. I use something like

  if (NILP (uname) || (strlen (SDATA (uname)) > 0))

uname is a Lisp_Object. SDATA (uname) returns (char *). What kind of
signedness do I break in strlen? Does anybody have an idea?

>> (dbus-get-unique-name :system)
>
> For example: ":1.2"
>
>> (dbus-get-unique-name :session)
>
> ":1.0"
>
>>
>> (dbus-list-names :system)
>
> ("org.freedesktop.DBus" ":1.1" ":1.2")
> ("org.freedesktop.DBus" ":1.2")
>
>
>> (dbus-list-names :session)
>
> ("org.freedesktop.DBus" ":1.0")
>
>>
>> (dbus-list-known-names :system)
>
> ("org.freedesktop.DBus")
>
>> (dbus-list-known-names :session)
>
> ("org.freedesktop.DBus")

All this means that dbusbind.c is working and there is no other D-Bus
application running. Too bad ...

Best regards, Michael.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]