unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: preparing the pretest
Date: Thu, 26 Sep 2002 07:17:26 +0200 (IST)	[thread overview]
Message-ID: <Pine.SUN.3.91.1020926071619.12918D-100000@is> (raw)
In-Reply-To: <E17uB4f-0006N7-00@pot.cnuce.cnr.it>


On Wed, 25 Sep 2002, Francesco Potorti` wrote:

> gcc -c -D_BSD_SOURCE   -Demacs -DHAVE_CONFIG_H -DUSE_LUCID  -I. -I/home/pot/gnu/emacs-pretest/src -D_BSD_SOURCE -I/usr/X11R6/include -g -O2 -DPURESIZE=5000000 -I../src dired.c
> In file included from dired.c:93:
> regex.h:541:1: warning: "__restrict_arr" redefined
> In file included from /usr/include/features.h:283,
>                  from /usr/lib/gcc-lib/i386-linux/3.2.1/include/stdio.h:37,
>                  from s/gnu-linux.h:157,
>                  from config.h:371,
>                  from dired.c:23:
> /usr/include/sys/cdefs.h:212:1: warning: this is the location of the previous definition
> 
> The warning does not appear when using gcc 2.95 (and did not appear with
> gcc 3.0).  The reason is that src/regex.h has this:
> 
> 
> ===File ~/gnu/emacs-pretest/src/regex.h=====================
> /* For now unconditionally define __restrict_arr to expand to nothing.
>    Ideally we would have a test for the compiler which allows defining
>    it to restrict.  */
> #define __restrict_arr

I suggest to make this definition conditional:

  #ifndef __restrict_arr
  #define __restrict_arr
  #endif

  reply	other threads:[~2002-09-26  5:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 12:15 preparing the pretest Francesco Potorti`
2002-09-26  5:17 ` Eli Zaretskii [this message]
2002-09-26 21:45   ` Richard Stallman
2002-09-30  8:13   ` Francesco Potorti`
2002-10-01  6:18     ` Richard Stallman

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=Pine.SUN.3.91.1020926071619.12918D-100000@is \
    --to=eliz@is.elta.co.il \
    --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).