unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Michael Albinus <michael.albinus@gmx.de>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: 23.0.50; dbus
Date: Sat, 5 Jan 2008 16:25:32 +0100	[thread overview]
Message-ID: <DC3E6DF4-81FD-4029-ACEB-074B75A69591@Freenet.DE> (raw)
In-Reply-To: <477CD505.3020906@swipnet.se>


Am 03.01.2008 um 13:28 schrieb Jan Djärv:

>
>
> Michael Albinus skrev:
>> Stefan Monnier writes:
>>>> Yes. But I still don't know what to do in the MacOS case, where  
>>>> tons of
>>>> compiler warnings are raised due to the signedness of the SDATA  
>>>> return
>>>> value. Peter has shown it in a recent message. Shall we always  
>>>> cast the
>>>> type like "strlen ((char *) SDATA (uname))"? This would affect  
>>>> much more
>>>> files but dbusbind.c.
>>> Use the -Wno-sign (or whatever its name is) to disable those  
>>> warnings.
>> "-Wno-pointer-sign" shall be good for I guess. It is enabled by  
>> default
>> in configure, when the compiler supports it.
>
> But only if you don't specify your own CFLAGS to configure.
>


Adding -Wno-pointer-sign to my CFLAGS set removes most of the  
warnings, no-one left for D-Bus!

--
Greetings

   Pete

A common mistake that people make when trying to design something  
completely foolproof is to underestimate the ingenuity of complete  
fools.

  reply	other threads:[~2008-01-05 15:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 12:00 23.0.50; dbus Peter Dyballa
2007-12-10 12:24 ` William Xu
2007-12-10 12:47   ` Jason Rumney
2007-12-10 12:56     ` Jason Rumney
2007-12-14 21:58 ` Michael Albinus
2007-12-15 10:41   ` Peter Dyballa
2007-12-16 22:57     ` Michael Albinus
2007-12-17 11:04       ` Peter Dyballa
2007-12-17 11:38         ` Michael Albinus
2007-12-21  0:05         ` Stefan Monnier
2007-12-21 19:49           ` Richard Stallman
2007-12-23 16:10       ` Peter Dyballa
2007-12-31 21:43         ` Michael Albinus
2007-12-31 22:26           ` Andreas Schwab
2008-01-01 10:46             ` Michael Albinus
2008-01-01 11:28               ` Peter Dyballa
2008-01-02  3:06           ` Stefan Monnier
2008-01-02  5:10             ` Michael Albinus
2008-01-02 11:40               ` Thien-Thi Nguyen
2008-01-02 12:48                 ` Michael Albinus
2008-01-02 13:41                   ` Thien-Thi Nguyen
2008-01-02 15:01               ` Stefan Monnier
2008-01-02 23:32                 ` Michael Albinus
2008-01-02 23:59                   ` Peter Dyballa
2008-01-03 12:28                   ` Jan Djärv
2008-01-05 15:25                     ` Peter Dyballa [this message]
2007-12-24 12:43       ` Peter Dyballa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DC3E6DF4-81FD-4029-ACEB-074B75A69591@Freenet.DE \
    --to=peter_dyballa@freenet.de \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=michael.albinus@gmx.de \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).