From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 34431@debbugs.gnu.org
Subject: bug#34431: Qt fails to build
Date: Tue, 12 Feb 2019 16:01:33 +0100 [thread overview]
Message-ID: <87sgwtjbjm.fsf@gnu.org> (raw)
In-Reply-To: <20190211124431.31f47135@scratchpost.org> (Danny Milosavljevic's message of "Mon, 11 Feb 2019 12:44:31 +0100")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> Possible fix https://672856.bugs.gentoo.org/attachment.cgi?id=557978
>
> diff -Naurp a/src/corelib/global/minimum-linux_p.h b/src/corelib/global/minimum-linux_p.h
> --- a/src/corelib/global/minimum-linux_p.h 2018-11-25 15:51:11.000000000 +0300
> +++ b/src/corelib/global/minimum-linux_p.h 2018-12-17 13:25:38.176823753 +0300
> @@ -75,14 +75,9 @@ QT_BEGIN_NAMESPACE
> * - accept4 2.6.28
> * - renameat2 3.16 QT_CONFIG(renameat2)
> * - getrandom 3.17 QT_CONFIG(getentropy)
> - * - statx 4.11 QT_CONFIG(statx)
> */
>
> -#if QT_CONFIG(statx)
> -# define MINLINUX_MAJOR 4
> -# define MINLINUX_MINOR 11
> -# define MINLINUX_PATCH 0
> -#elif QT_CONFIG(getentropy)
> +#if QT_CONFIG(getentropy)
> # define MINLINUX_MAJOR 3
> # define MINLINUX_MINOR 17
> # define MINLINUX_PATCH 0
Qt should definitely not require a kernel more recent than what libc
requires. If this patch solves that, we should probably apply it (in
‘staging’ I guess.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-02-12 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 11:20 bug#34431: Qt fails to build Andreas Enge
2019-02-11 11:41 ` Danny Milosavljevic
2019-02-11 15:27 ` Andreas Enge
2019-02-12 11:08 ` Andreas Enge
2019-02-11 11:44 ` Danny Milosavljevic
2019-02-12 15:01 ` Ludovic Courtès [this message]
2019-02-12 16:59 ` Ricardo Wurmus
2019-02-13 23:32 ` Andreas Enge
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=87sgwtjbjm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34431@debbugs.gnu.org \
--cc=dannym@scratchpost.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/guix.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.