unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Nelson H. F. Beebe" <beebe@math.utah.edu>, emacs-devel@gnu.org
Subject: Re: [platform-testers] Emacs 26.2 RC1 is out!
Date: Fri, 22 Mar 2019 06:54:04 -0600	[thread overview]
Message-ID: <CMM.0.96.0.1553259244.beebe@gamma.math.utah.edu> (raw)
In-Reply-To: <834l7vtlp0.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> asks about the Solaris 11.4 problem in
building emacs-26.2: the lmcs2.h header file is not found, because it
is expected in /usr/include, but actually stored in /usr/include/lcms:

>> Does that system have an lcms2/pc file and pkg-config, and does the
>> following command show the correct -I switch:
>>
>> pkg-config --cflags lcms2

The file

	/usr/gnu/lib/pkgconfig/lcms2.pc

is supplied by Oracle in Solaris 11.4, and the command reports

	% pkg-config --cflags lcms2
	-I/usr/include/lcms

So, it seems to be a reasonable solution to have configure.ac
use pkg-config to find the needed -I option.

Eli also asks:

>> I believe Emacs 26.1 also doesn't compile on that system for the
>> same reason?

I tried a similar build of emacs-26.1 on Solaris 11.4 with

	set path= ( /opt/developerstudio12.6/bin /bin )
	env CC=cc ./configure --prefix=$prefix --with-gnutls=no --with-pop --with-gif=no && gmake all check

It too fails with

	  CC       lcms.o
	"lcms.c", line 23: cannot find include file: <lcms2.h>

I ran

	gmake CFLAGS="-I${prefix}/include -I/usr/include/lcms"

and got a build and installation to complete.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe@math.utah.edu  -
- 155 S 1400 E RM 233                       beebe@acm.org  beebe@computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------



  reply	other threads:[~2019-03-22 12:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 22:35 [platform-testers] Emacs 26.2 RC1 is out! Nelson H. F. Beebe
2019-03-22  7:25 ` Eli Zaretskii
2019-03-22 12:54   ` Nelson H. F. Beebe [this message]
2019-03-22 13:29     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2019-03-22 12:25 Nelson H. F. Beebe
2019-03-21 16:25 Nelson H. F. Beebe
2019-03-21 17:03 ` Eli Zaretskii
2019-03-22  1:08 ` Stefan Monnier
2019-03-22  7:37   ` Eli Zaretskii
2019-03-22 12:20     ` Stefan Monnier
2019-03-22 13:19       ` Eli Zaretskii
2019-03-22 13:58         ` Stefan Monnier
2019-03-25 17:50   ` Paul Eggert
2019-03-22  3:36 ` Van L

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=CMM.0.96.0.1553259244.beebe@gamma.math.utah.edu \
    --to=beebe@math.utah.edu \
    --cc=eliz@gnu.org \
    --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).