linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	Boris Barbulovski <bbarbulovski@gmail.com>,
	Thiago Macieira <thiago.macieira@intel.com>
Subject: Re: linux-next: Tree for Nov 1 (xconfig problem)
Date: Mon, 2 Nov 2015 14:39:16 +0100	[thread overview]
Message-ID: <56376784.3030804@suse.cz> (raw)
In-Reply-To: <5636D465.4060104@infradead.org>

On 2015-11-02 04:11, Randy Dunlap wrote:
> On 11/01/15 08:53, Stephen Rothwell wrote:
>> Hi all,
>>
>> I start again a day early, and this is how you all repay me? ;-)
>>
>> Changes since 20151022:
>>
> 
> on x86_64:
> 
> 'make xconfig' dies a quick death when I try to use it:
> 
> linux-next-20151101> ASSERT: "!isEmpty()" in file /usr/include/QtCore/qlist.h, line 282

Added Boris and Thiago to Cc.

Are you using Qt4 or Qt5? An

  ldd scripts/kconfig/qconf | grep Qt

will tell you.

Michal

  reply	other threads:[~2015-11-02 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 16:53 linux-next: Tree for Nov 1 Stephen Rothwell
2015-11-02  1:16 ` linux-next: Tree for Nov 1 (lightnvm) Randy Dunlap
2015-11-02 12:43   ` Matias Bjorling
2015-11-02 15:37     ` Jens Axboe
2015-11-02 22:34       ` Matias Bjorling
2015-11-03 16:53         ` Jens Axboe
2015-11-02  3:11 ` linux-next: Tree for Nov 1 (xconfig problem) Randy Dunlap
2015-11-02 13:39   ` Michal Marek [this message]
2015-11-02 13:51     ` Thiago Macieira
2015-11-02 16:44       ` Randy Dunlap
2015-11-02 16:58         ` Thiago Macieira
2015-11-02 18:48           ` Randy Dunlap
2015-11-02 19:23             ` Thiago Macieira
2015-11-02 20:42               ` Michal Marek
2015-11-02 16:01     ` Randy Dunlap
2015-11-02  8:04 ` linux-next: Tree for Nov 1 Geert Uytterhoeven

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=56376784.3030804@suse.cz \
    --to=mmarek@suse.cz \
    --cc=bbarbulovski@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=thiago.macieira@intel.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 NNTP newsgroup(s).