[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#30193: crash in libotf
From: |
handa |
Subject: |
bug#30193: crash in libotf |
Date: |
Sun, 28 Jan 2018 20:57:52 +0900 |
In article <ak1sicymx9.fsf@fencepost.gnu.org>, Glenn Morris <rgm@gnu.org>
writes:
> handa wrote:
> > 1. Check the version number of libotf in configure script.
> > 2. Expose that version number to config.h.
Sorry for that. Directly checking the following macros of <otf.h> is
easier.
/* Version name of this library. */
#define LIBOTF_VERSION "0.9.15"
/* Major version number. */
#define LIBOTF_MAJOR_VERSION 0
/* Minor version number. */
#define LIBOTF_MINOR_VERSION 9
/* Release (i.e. patch level) number. */
#define LIBOTF_RELEASE_NUMBER 16
> > 3. In xfaces.c, if the version number is less than 0.9.16, initialize
> > Vface_ignored_fonts to ("Noto Serif Kannada").
> Thanks, done in 2ce56c51a8.
> It seems like a run-time test would be better.
> (Will libotf 0.9.16 have an soname version bump?)
Yes. The current library is libotf.so.0 (linked to libotf.so.0.0), but
the new one will be libotf.so.1 (linked to libotf.so.1.0.0).
---
K. Handa
handa@gnu.org
- bug#30193: The deadliest file in Emacs history, (continued)
- bug#30193: The deadliest file in Emacs history, Eli Zaretskii, 2018/01/21
- bug#30193: crash in libotf, Glenn Morris, 2018/01/21
- bug#30193: crash in libotf, handa, 2018/01/23
- bug#30193: crash in libotf, Glenn Morris, 2018/01/23
- bug#30193: crash in libotf, handa, 2018/01/25
- bug#30193: crash in libotf, Eli Zaretskii, 2018/01/25
- bug#30193: crash in libotf, handa, 2018/01/26
- bug#30193: crash in libotf, Eli Zaretskii, 2018/01/26
- bug#30193: crash in libotf, handa, 2018/01/28
- bug#30193: crash in libotf, Glenn Morris, 2018/01/26
- bug#30193: crash in libotf,
handa <=
bug#30193: The deadliest file in Emacs history, 積丹尼 Dan Jacobson, 2018/01/21