From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: Ubuntu 16.04 cannot compile commit c4687d920db081f29e93cca8156793d545a827e2
Date: Sat, 25 Jan 2020 23:20:01 +0100 [thread overview]
Message-ID: <87blqrdvqm.fsf@mat.ucm.es> (raw)
In-Reply-To: jwvblqtoroe.fsf-monnier+emacs@gnu.org
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> pkg_cv_LIBOTF_LIBS='-lfreetype -lz -lpng12 -lotf -lfreetype'
> [...]
>> LIBOTF_LIBS='-lfreetype -lz -lpng12 -lotf -lfreetype'
> I think this is part of the answer: why do the OTF settings ask for
> a `png12` library?
Ok I could finally do some testing.
I tried again to ./configure and compile master from December 2019 and
from August 2019 which I have compiled without a problem.
And it is the same problem, although now png16 is installed configure,
sets the flag to png12.
I presume before my upgrade, I had png12.
I am not sure how to deal with it.
1. I don't want to run --without-png
2. I don't want to desinstall png16 (which would be effectively the
same, at least for emacs compiling)
Any ideas?
Uwe Brauer
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-01-25 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 20:09 Ubuntu 16.04 cannot compile commit c4687d920db081f29e93cca8156793d545a827e2 Uwe Brauer
2020-01-24 8:47 ` Paul Eggert
2020-01-24 8:52 ` Uwe Brauer
2020-01-24 9:20 ` Robert Pluim
2020-01-24 9:29 ` Paul Eggert
2020-01-24 10:21 ` Uwe Brauer
2020-01-24 13:28 ` Eli Zaretskii
2020-01-24 14:28 ` Stefan Monnier
2020-01-24 16:18 ` Uwe Brauer
2020-01-25 22:20 ` Uwe Brauer [this message]
2020-01-25 22:48 ` Stefan Monnier
2020-01-26 8:01 ` Paul Eggert
2020-01-26 8:42 ` [SOLVED (sort of)] (was: Ubuntu 16.04 cannot compile commit c4687d920db081f29e93cca8156793d545a827e2) Uwe Brauer
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=87blqrdvqm.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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 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.