all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "WAROQUIERS Philippe" <philippe.waroquiers@eurocontrol.int>
Cc: schwab@suse.de, emacs-devel@gnu.org, rgm@gnu.org
Subject: Re: [philippe.waroquiers@eurocontrol.int: RE: emacs 22.1 on hp-ux 11.11 core dumps when DISPLAY not set]
Date: Fri, 17 Aug 2007 00:49:51 -0400	[thread overview]
Message-ID: <E1ILtmR-0002oP-9K@fencepost.gnu.org> (raw)
In-Reply-To: <1B2B2EF98D55CB41BD16F13B18B9B0080303EE83@FFBRUE001.cfmu.corp.eurocontrol.int> (philippe.waroquiers@eurocontrol.int)

    Note that in emacs src directory, doing :
      grep '^  *static ' *.c
    finds something like 140 occurences of static vars in functions.
    (maybe most of these occurences are in some code not used on USG systems
    ?)

We should check all of these to make sure that none of them can be
used on systems that do `#define static '.  If any can be used there,
we need to change the code.

But there is another possibility.  Maybe we can get rid of the
practice of #define static.

I wonder if recent versions of HPUX still need the #define static.
How about if you try deleting that from hpux.h, and rebuild Emacs, and
see if it works?

I see that s/usg5-4.h does #undef static.
Are any pre-5.4 USG systems still used?
Are any really still supported?

It would be nice to get rid of that issue.

      reply	other threads:[~2007-08-17  4:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 23:11 [philippe.waroquiers@eurocontrol.int: RE: emacs 22.1 on hp-ux 11.11 core dumps when DISPLAY not set] Richard Stallman
2007-08-15  2:43 ` Glenn Morris
2007-08-15  2:46   ` Glenn Morris
     [not found]   ` <E1ILNVk-0007Gh-IH@fencepost.gnu.org>
2007-08-15 18:38     ` Andreas Schwab
2007-08-16 21:00       ` WAROQUIERS Philippe
2007-08-17  4:49         ` Richard Stallman [this message]

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

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

  git send-email \
    --in-reply-to=E1ILtmR-0002oP-9K@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philippe.waroquiers@eurocontrol.int \
    --cc=rgm@gnu.org \
    --cc=schwab@suse.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.