From: Rob Browning <rlb@defaultvalue.org>
Cc: emacs-devel@gnu.org
Subject: Re: config related patch (and how to start handling Debian patches)
Date: Fri, 14 Feb 2003 23:11:58 -0600 [thread overview]
Message-ID: <87el6ann4x.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E18iMZ5-0000ls-00@fencepost.gnu.org> (Richard Stallman's message of "Mon, 10 Feb 2003 17:38:15 -0500")
Richard Stallman <rms@gnu.org> writes:
> The current pretest is from a branch that has only bug fixes.
> The place we would install changes like these is in the CVS trunk,
> so please make them fit in there.
OK. I've switched to cvs HEAD, and it looks like two of the three
patches are now redundant.
This small patch switches emacs to prefer the mem* functions rather
than the b* functions when they're available since at least under
GNU/Linux, the b* appear to be deprecated. However, if this
deprecation isn't common, the following patch might not be the right
thing to do.
Index: configure.in
===================================================================
RCS file: /cvsroot/emacs/emacs/configure.in,v
retrieving revision 1.326
diff -u -r1.326 configure.in
--- configure.in 4 Feb 2003 14:56:31 -0000 1.326
+++ configure.in 15 Feb 2003 04:55:35 -0000
@@ -2206,7 +2206,8 @@
utimes setrlimit setpgid getcwd getwd shutdown strftime getaddrinfo \
__fpending mblen mbrlen mbsinit strsignal setitimer ualarm index rindex \
sendto recvfrom getsockopt setsockopt getsockname getpeername \
-gai_strerror mkstemp getline getdelim mremap memmove fsync bzero memset)
+gai_strerror mkstemp getline getdelim mremap memmove fsync bzero \
+memset memcmp memmove)
AC_CHECK_HEADERS(sys/un.h)
@@ -2823,14 +2824,16 @@
# endif
#endif
-#ifndef HAVE_BCOPY
-#define bcopy(a,b,s) memcpy (b,a,s)
-#endif
-#ifndef HAVE_BZERO
-#define bzero(a,s) memset (a,0,s)
-#endif
-#ifndef HAVE_BCMP
-#define BCMP memcmp
+/* avoid deprecated functions */
+#if HAVE_MEMCPY
+# define bcopy(a,b,s) memcpy (b,a,s)
+#endif
+#if HAVE_MEMSET
+# define bzero(a,s) memset (a,0,s)
+#endif
+#if HAVE_MEMCMP
+# define BCMP memcmp
+# define bcmp memcmp
#endif
#endif /* EMACS_CONFIG_H */
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2003-02-15 5:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 23:06 config related patch (and how to start handling Debian patches) Rob Browning
2003-02-09 12:40 ` Richard Stallman
2003-02-09 17:54 ` Rob Browning
2003-02-10 22:38 ` Richard Stallman
2003-02-15 5:11 ` Rob Browning [this message]
2003-02-15 18:01 ` Benjamin Riefenstahl
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=87el6ann4x.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=emacs-devel@gnu.org \
/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).