unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gabriele Svelto <gabriele.svelto@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>,
	Joakim Jalap <joakim.jalap@fastmail.com>
Cc: 22385-done@debbugs.gnu.org
Subject: bug#22385: 24.5; Build failure with modules on OpenBSD
Date: Mon, 18 Jan 2016 00:58:30 +0100	[thread overview]
Message-ID: <569C2AA6.8030802@gmail.com> (raw)
In-Reply-To: <569C1616.5030603@cs.ucla.edu>

 Hello Paul,
thanks for getting in touch about this. There's a way to fix this issue
in my macro and it's by running the test twice with and without the
attribute and comparing the compiler error output instead of simply
assuming that any error output means that the attribute is not
supported. It's something I had considered doing in the beginning but
deemed unnecessarily complicated at the time. Turns out I was wrong;
I'll try to push a fix into autoconf-archive in the next few days.

 Gabriele

On 17/01/2016 23:30, Paul Eggert wrote:
> Thanks for reporting the problem. The OpenBSD compiler warnings about
> strcpy etc. are false alarms, and these false alarms confuse the Emacs
> build procedure and therefore introduce bugs into the Emacs module code.
> We're lucky that a run-time assertion caught this.
> 
> I installed the attached patch into the emacs-25 branch. It removes the
> offending test in 'configure', and so should fix the bug so I am boldly
> marking it as done. Please give the fix a try; if it doesn't work I can
> unmark the bug.
> 
> Is there some way to tell the OpenBSD C compiler to not chatter about
> uses of strcpy, strcat, and sprintf? We don't want to use the
> OpenBSD-suggested replacements in Emacs, as that would be more likely to
> introduce bugs than to fix them. If we can suggest (or get 'configure'
> to use) a build-time option to suppress the false alarms that would save
> everybody some work and would help make Emacs more reliable.
> 
> Although the OpenBSD porting problem with AX_GCC_VAR_ATTRIBUTE no longer
> affects Emacs, it might affect other programs that use that macro, so
> I'll CC: this to the macro's author Gabriele Svelto. Gabriele, the bug
> report is here:
> 
> http://bugs.gnu.org/22385






      reply	other threads:[~2016-01-17 23:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 17:43 bug#22385: 24.5; Build failure with modules on OpenBSD Joakim Jalap
2016-01-17 16:22 ` Philipp Stephani
2016-01-17 22:30 ` Paul Eggert
2016-01-17 23:58   ` Gabriele Svelto [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

  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=569C2AA6.8030802@gmail.com \
    --to=gabriele.svelto@gmail.com \
    --cc=22385-done@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=joakim.jalap@fastmail.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).