all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: 28893@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#28893: emacs-26.0.90 minor build issue on OpenIndiana
Date: Tue, 31 Oct 2017 08:08:23 -0400	[thread overview]
Message-ID: <87r2tja5ag.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CMM.0.96.0.1508864580.beebe@gamma.math.utah.edu> (Nelson H. F. Beebe's message of "Tue, 24 Oct 2017 11:03:00 -0600")

tags 9736 fixed
close 9736 26.1
quit

"Nelson H. F. Beebe" <beebe@math.utah.edu> writes:

> Paul Eggert proposes a small patch to the emacs-26.0.90 configure
> script to deal with the build problem that I reported for OpenIndiana.
>
> I've just done a fresh build on that system, and Paul's patch solves
> the problem:

Okay, closing.

> I suggest, however, that configure.ac acquire some explanatory
> comments to document why -lcurses should be searched before -ltermcap
> on OpenIndiana.

A later commit [1: 19667f44ef], adds a mention of OpenIndiana, and the
existing reference to Bug#9736 explains the reasoning for AIX (AFAICT,
the library situation is the same on both these OSes).

[1: 19667f44ef]: 2017-10-24 11:46:53 -0700
  * configure.ac: Tweak libcurses diagnostic.
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=19667f44efabda7d4e53e706c6cd8140145b2a1a





      reply	other threads:[~2017-10-31 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 20:53 bug#28893: emacs-26.0.90 minor build issue on OpenIndiana Nelson H. F. Beebe
2017-10-19  1:39 ` Noam Postavsky
2017-10-23  5:53 ` Paul Eggert
2017-10-24 17:03   ` Nelson H. F. Beebe
2017-10-31 12:08     ` Noam Postavsky [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=87r2tja5ag.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=28893@debbugs.gnu.org \
    --cc=beebe@math.utah.edu \
    --cc=eggert@cs.ucla.edu \
    /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.