unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: noloader@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Failed compile due to security_context_t and friends on CentOS 5
Date: Fri, 05 Jan 2018 22:19:46 -0500	[thread overview]
Message-ID: <0c1sj3fzcd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAH8yC8=hTxu9v1ckxX9eHJzOy11D1vZxV-7KxJOWu0dvHPJ_Fw@mail.gmail.com> (Jeffrey Walton's message of "Wed, 3 Jan 2018 18:20:58 -0500")

Jeffrey Walton wrote:

> I'm building Emacs 24.5 from sources on CentOS 5.

(As an aside, your distribution was EOL'd 9 months ago:
https://lists.centos.org/pipermail/centos-announce/2017-April/022350.html )

> Does anyone know how to avoid the build failures for this platform?

Adding "--without-selinux" to the configure options is probably the
easiest fix.

> fileio.c: In function 'Fcopy_file':
> fileio.c:1944: error: 'security_context_t' undeclared (first use in
> this function)



      reply	other threads:[~2018-01-06  3:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 23:20 Failed compile due to security_context_t and friends on CentOS 5 Jeffrey Walton
2018-01-06  3:19 ` Glenn Morris [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=0c1sj3fzcd.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=noloader@gmail.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.
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).