From: Eli Zaretskii <eliz@gnu.org>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Compiler warnings in latest CVS
Date: Sat, 26 Jan 2008 15:35:26 +0200 [thread overview]
Message-ID: <usl0klnfl.fsf@gnu.org> (raw)
In-Reply-To: <m3y7b1gze6.fsf@cam.ac.uk> (message from Leo on Mon, 07 Jan 2008 20:21:37 +0000)
> From: Leo <sdl.web@gmail.com>
> Date: Mon, 07 Jan 2008 20:21:37 +0000
>
> I am seeing tons of warning messages similar to the following when
> compiling Emacs in Fedora 8.
>
> ,----
> | coding.c:3475: warning: pointer targets in passing argument 1 of 'safe_bcopy' differ in signedness
> `----
Does it help to cast the arguments of 'safe_bcopy' to (char *) ?
> the warnings of .c files have increased considerably.
Please report all the warnings, and thanks.
next prev parent reply other threads:[~2008-01-26 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 20:21 Compiler warnings in latest CVS Leo
2008-01-26 13:35 ` Eli Zaretskii [this message]
2008-01-26 19:33 ` Stefan Monnier
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=usl0klnfl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.com \
/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).