From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 1/4] qt4: fix compile error in Qt 4.8.0 with gcc 4.6
Date: Fri, 10 Feb 2012 14:03:06 +0000 [thread overview]
Message-ID: <1328882587.14363.87.camel@phil-desktop> (raw)
In-Reply-To: <1440799.NqLiKZanR0@helios>
On Fri, 2012-02-10 at 13:56 +0000, Paul Eggleton wrote:
> What the code is attempting to do is provide its own "nullptr" if it isn't
> being provided as part of the language:
>
> ------------------------------
> #if __has_feature(cxx_nullptr) || (GCC_VERSION_AT_LEAST(4, 6, 0) && defined(__GXX_EXPERIMENTAL_CXX0X__)) || (defined(_MSC_VER) && _MSC_VER >= 1600 && !COMPILER(INTEL))
>
> #define HAVE_NULLPTR 1
>
> #else
>
> namespace std {
> class nullptr_t { };
> }
>
> extern std::nullptr_t nullptr;
>
> #endif
> ------------------------------
>
> gcc 4.6 is preempting this and complaining about the use of the identifier. I
> don't think renaming it is going to be acceptable upstream either.
Does it work if you build with -std=c++0x? If Qt is doing the above
then presumably it is at least attempting to be compatible with C++0X.
p.
next prev parent reply other threads:[~2012-02-10 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 17:57 [RFC PATCH 0/4] qmake/qt4-tools-nativesdk fixes Paul Eggleton
2012-02-09 17:57 ` [RFC PATCH 1/4] qt4: fix compile error in Qt 4.8.0 with gcc 4.6 Paul Eggleton
2012-02-09 21:19 ` Khem Raj
2012-02-10 13:56 ` Paul Eggleton
2012-02-10 14:03 ` Phil Blundell [this message]
2012-02-10 14:09 ` Paul Eggleton
2012-02-10 19:31 ` Paul Eggleton
2012-02-10 20:36 ` Khem Raj
2012-02-09 17:57 ` [RFC PATCH 2/4] qt4: build qmake for the target Paul Eggleton
2012-02-09 18:18 ` Koen Kooi
2012-02-09 18:22 ` Paul Eggleton
2012-02-09 17:57 ` [RFC PATCH 3/4] qt4-tools-nativesdk: fix build of 4.7.4 Paul Eggleton
2012-02-09 17:57 ` [RFC PATCH 4/4] qt4-tools-nativesdk: improve and tidy up qmake build Paul Eggleton
2012-02-09 18:07 ` [RFC PATCH 0/4] qmake/qt4-tools-nativesdk fixes Otavio Salvador
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=1328882587.14363.87.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox