From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs master build failing on RHEL 6.8
Date: Tue, 7 May 2019 10:41:55 -0400 [thread overview]
Message-ID: <CAFyQvY2i5HFFdrAZ_3CV4u-oOxUXpOYF0AXG2wxW1VuP2P0ORg@mail.gmail.com> (raw)
In-Reply-To: <834l66jpty.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On Tue, May 7, 2019 at 10:34 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> What version of librsvg do you have there, and what does the
> LIBRSVG_CHECK_VERSION macro look like in its headers?
>
km²/usr:include/librsvg-2>
pwd 05/07
10:39am
/usr/include/librsvg-2
km²/usr:include/librsvg-2> rg
VERSION 05/07 10:40am
librsvg/librsvg-features.h
4:#define LIBRSVG_MAJOR_VERSION (2)
5:#define LIBRSVG_MINOR_VERSION (26)
6:#define LIBRSVG_MICRO_VERSION (0)
7:#define LIBRSVG_VERSION ""
9:#define LIBRSVG_CHECK_VERSION(major,minor,micro) \
10: (LIBRSVG_MAJOR_VERSION > (major) || \
11: (LIBRSVG_MAJOR_VERSION == (major) && LIBRSVG_MINOR_VERSION > (minor))
|| \
12: (LIBRSVG_MAJOR_VERSION == (major) && LIBRSVG_MINOR_VERSION == (minor)
&& LIBRSVG_MICRO_VERSION >= (micro)))
The version is 2.26.0.
I see " #define LIBRSVG_CHECK_VERSION(major,minor,micro) \" .. note that
there is no space before the opening bracket .. is that detail important?
[-- Attachment #2: Type: text/html, Size: 1649 bytes --]
next prev parent reply other threads:[~2019-05-07 14:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 12:00 Emacs master build failing on RHEL 6.8 Kaushal Modi
2019-05-07 14:34 ` Eli Zaretskii
2019-05-07 14:41 ` Kaushal Modi [this message]
2019-05-07 15:13 ` Eli Zaretskii
2019-05-07 15:30 ` Stefan Monnier
2019-05-07 15:52 ` Eli Zaretskii
2019-05-07 16:01 ` Kaushal Modi
2019-05-07 18:22 ` Eli Zaretskii
2019-05-07 19:46 ` Kaushal Modi
2019-05-08 5:47 ` Eli Zaretskii
2019-05-08 8:03 ` Andreas Schwab
2019-05-08 11:42 ` Kaushal Modi
2019-05-08 12:27 ` Eli Zaretskii
2019-05-08 12:49 ` Kaushal Modi
2019-05-08 13:05 ` Eli Zaretskii
2019-05-08 15:07 ` Kaushal Modi
2019-05-08 15:41 ` Paul Eggert
2019-05-08 15:50 ` Kaushal Modi
2020-02-14 19:49 ` WilliamKF
2020-02-14 20:44 ` Paul Eggert
2019-05-07 18:49 ` Mattias Engdegård
2019-05-08 15:57 ` Paul Eggert
2019-05-08 17:16 ` CPP indentation bikeshed (was: Emacs master build failing on RHEL 6.8) Stefan Monnier
2019-05-09 4:25 ` Paul Eggert
2019-05-07 17:37 ` Emacs master build failing on RHEL 6.8 martin rudalics
2019-05-07 18:20 ` Eli Zaretskii
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=CAFyQvY2i5HFFdrAZ_3CV4u-oOxUXpOYF0AXG2wxW1VuP2P0ORg@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=eggert@cs.ucla.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).