From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygport compile command fails
Date: Wed, 15 Dec 2021 14:56:36 +0100 [thread overview]
Message-ID: <87k0g6dl9n.fsf@Otto.invalid> (raw)
In-Reply-To: <1385850692.28506.1639561032910.JavaMail.yahoo@mail.yahoo.co.jp> (Tatsuro MATSUOKA's message of "Wed, 15 Dec 2021 18:37:12 +0900 (JST)")
Tatsuro MATSUOKA writes:
>> > In file included from /usr/src/qt5-base-5.9.4-2.src/qt5-base-5.9.4-2.x86_64/src/qtbase-opensource-src-5.9.4/src/corelib/tools/qbytearray.cpp:42:
>> > /usr/src/qt5-base-5.9.4-2.src/qt5-base-5.9.4-2.x86_64/src/qtbase-opensource-src-5.9.4/src/corelib/tools/qbytearraymatcher.h: In static member function ‘static QStaticByteArrayMatcherBase::Skiptable QStaticByteArrayMatcherBase::generate(const char*, uint)’:
>> > /usr/src/qt5-base-5.9.4-2.src/qt5-base-5.9.4-2.x86_64/src/qtbase-opensource-src-5.9.4/src/corelib/tools/qbytearraymatcher.h:103:38: error: ‘numeric_limits’ is not a member of ‘std’
>> > 103 | const auto uchar_max = (std::numeric_limits<uchar>::max)();
>> > | ^~~~~~~~~~~~~~
>> > /usr/src/qt5-base-5.9.4-2.src/qt5-base-5.9.4-2.x86_64/src/qtbase-opensource-src-5.9.4/src/corelib/tools/qbytearraymatcher.h:103:58: error: expected primary-expression before ‘>’ token
>> > 103 | const auto uchar_max = (std::numeric_limits<uchar>::max)();
>> > | ^
>> > /usr/src/qt5-base-5.9.4-2.src/qt5-base-5.9.4-2.x86_64/src/qtbase-opensource-src-5.9.4/src/corelib/tools/qbytearraymatcher.h:103:61: error: ‘::max’ has not been declared; did you mean ‘std::max’?
>> > 103 | const auto uchar_max = (std::numeric_limits<uchar>::max)();
>> > | ^~~
>> > | std::max
The default C++ standard targeted by gcc-11 is gnu++17.
Given how old Qt5 is and that the upstream packages were compiled w/
gcc-7 mostly, I'd guess you should either add -std=gnu++11 or
-std=gnu++14 to the CXXFLAGS.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2021-12-15 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1385850692.28506.1639561032910.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2021-12-15 9:37 ` Tatsuro MATSUOKA
2021-12-15 13:56 ` ASSI [this message]
[not found] <42772227.153689.1639737354375.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2021-12-17 10:35 ` Tatsuro MATSUOKA
2021-12-18 10:19 ` Achim Gratz
[not found] <604706974.1625790.1639515893094.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2021-12-14 21:04 ` Tatsuro MATSUOKA
2021-12-14 21:14 ` Marco Atzeri
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=87k0g6dl9n.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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.
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).