From: Michal Marek <mmarek@suse.cz>
To: Tiana Rakotovao Andriamahefa <rkmahefa@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: kconfig: qconf.cc: fix a compiliation error when using make xconfig
Date: Tue, 15 Jan 2013 22:32:34 +0100 [thread overview]
Message-ID: <50F5CAF2.1050207@suse.cz> (raw)
In-Reply-To: <20130114005449.GA5499@rak.local>
On 14.1.2013 01:54, Tiana Rakotovao Andriamahefa wrote:
> Le dimanche 13 janvier 2013 à 09:50:52, Michal Marek a écrit :
>> On 13.1.2013 04:28, Tiana Rakotovao Andriamahefa wrote:
>>> When using make xconfig, the following compilation error appears :
>>> /usr/include/qt3/qvaluelist.h:427:13: error: ‘ptrdiff_t’ does not name a type
>>> Including stddef.h in scripts/kconfig/qconf.cc permits to avoid this error.
>>
>> This is a bug in the Qt header. Is Qt3 still maintained?
>
> This seems to be a common c++ issue since the begining of 2011.
>
> Some Qt3 headers use ptrdiff_t which is defined in stddef.h. They also use some
> c++ headers, and rely on them to include stddef.h. However, since GCC-4.6,
> those c++ headers do not include stddef.h anymore. So, include <stddef.h>
> fixes it.
Right. My question is - is Qt3 still maintained somehow, so the includes
can be added where they belong, or do we need to workaround in in the
applications?
Michal
next prev parent reply other threads:[~2013-01-15 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 3:28 [PATCH] scripts: kconfig: qconf.cc: fix a compiliation error when using make xconfig Tiana Rakotovao Andriamahefa
2013-01-13 20:50 ` Michal Marek
2013-01-14 0:54 ` Tiana Rakotovao Andriamahefa
2013-01-15 21:32 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-24 16:20 Tiana Rakotovao Andriamahefa
2013-01-30 9:17 ` Michal Marek
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=50F5CAF2.1050207@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkmahefa@gmail.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