From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: 27bb4de72b * Port cleanup attribute to Oracle Studio 12.5
Date: Fri, 16 Jun 2017 16:34:35 +0000 [thread overview]
Message-ID: <CAArVCkQJmJZkAeg2Jd18CkMvFeyxTO30_8vOBheMzu+EMhdPvA@mail.gmail.com> (raw)
In-Reply-To: <945936bf-42a6-93f8-7b8d-63cdac42c6ee@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am Do., 15. Juni 2017 um 22:33 Uhr:
> On 06/15/2017 12:20 PM, Philipp Stephani wrote:
> > we might even compile emacs-modules.c as C++ unconditionally. I guess
> > by now every system that has a C compiler and supports shared
> > libraries also has a C++ compiler.
>
> Although C++ compilers may be available, they (or their libraries) are
> not necessarily installed properly, and this can be a problem at runtime
> as well as at compile-time. So it may be better to stick with C if it
> works.
>
OK, let's keep the code as is for now; once we find a platform that causes
problems, we can reevaluate the options.
>
> > (i.e. this doesn't even need --enable-gcc-warnings)
> >
>
> Ah, that's key. Although 'configure' suppresses that false alarm if
> --enable-gcc-warnings is specified, it also needs to suppress it when
> --enable-gcc-warnings is *not* specified. I installed the attached,
> which I hope fixes the warnings that were annoying you (assuming we are
> not using -save-temps, which is a reasonable assumption).
>
OK, thanks.
[-- Attachment #2: Type: text/html, Size: 1588 bytes --]
next prev parent reply other threads:[~2017-06-16 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 10:29 27bb4de72b * Port cleanup attribute to Oracle Studio 12.5 Philipp Stephani
2017-06-14 18:25 ` Paul Eggert
2017-06-15 12:54 ` Philipp Stephani
2017-06-15 18:46 ` Paul Eggert
2017-06-15 19:20 ` Philipp Stephani
2017-06-15 20:33 ` Paul Eggert
2017-06-16 16:34 ` Philipp Stephani [this message]
2017-06-16 3:19 ` Richard Stallman
2017-06-20 19:18 ` Paul Eggert
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=CAArVCkQJmJZkAeg2Jd18CkMvFeyxTO30_8vOBheMzu+EMhdPvA@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=eggert@cs.ucla.edu \
--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).