From: Tomi Ollila <tomi.ollila@iki.fi>
To: Michael J Gruber <git@grubix.eu>, notmuch@notmuchmail.org
Subject: Re: [PATCH] fix FTBFS with glib
Date: Fri, 12 Feb 2021 20:48:27 +0200 [thread overview]
Message-ID: <m2lfbtunpg.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <aee618a3d41f7889a7449aa16893e992325a909a.1613055071.git.git@grubix.eu>
On Thu, Feb 11 2021, Michael J. Gruber wrote:
> With newer glib, notmuch FTBFS because of C linkage error. This is due
If/when the alternative change is send (if it works), then it would be
nice if this FTBFS were opened (i searched it but deliberately leave
it still a mystery for some of us ;)
Tomi
> to a misplaced include (inside an extern "C") which was always there
> but exposed only recently through this change in glib:
>
> https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1715
>
> Move to the include to the outside of the extern block.
>
> Signed-off-by: Michael J Gruber <git@grubix.eu>
> ---
> lib/notmuch-private.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/notmuch-private.h b/lib/notmuch-private.h
> index 2fbf7ab9..46845253 100644
> --- a/lib/notmuch-private.h
> +++ b/lib/notmuch-private.h
> @@ -31,6 +31,8 @@
>
> #include "notmuch.h"
>
> +#include "gmime-extra.h"
> +
> NOTMUCH_BEGIN_DECLS
>
> #include <stdlib.h>
> @@ -47,8 +49,6 @@ NOTMUCH_BEGIN_DECLS
>
> #include <talloc.h>
>
> -#include "gmime-extra.h"
> -
> #include "xutil.h"
> #include "error_util.h"
> #include "string-util.h"
> --
> 2.30.0.368.g1c478ce6f6
next prev parent reply other threads:[~2021-02-12 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 14:51 [PATCH] fix FTBFS with glib Michael J Gruber
2021-02-12 12:57 ` David Bremner
2021-02-12 15:01 ` Michael J Gruber
2021-02-12 18:48 ` Tomi Ollila [this message]
2021-02-12 19:51 ` Michael J Gruber
2021-02-13 21:22 ` [PATCH] fix build failure with glib 2.67 David Bremner
2021-02-15 20:59 ` David Bremner
2021-02-15 21:29 ` Michael J Gruber
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lfbtunpg.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=git@grubix.eu \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).