From: jimmy bahuleyan <knight.camelot@gmail.com>
To: linux-kernel@vger.kernel.org, sam@ravnborg.org, zippel@linux-m68k.org
Subject: make xconfig failure on 2.6.21.5
Date: Sun, 24 Jun 2007 00:14:49 +0530 [thread overview]
Message-ID: <467D6A21.8020507@gmail.com> (raw)
Hi,
I have a Kubuntu 7.04 distro with Qt4 development packages installed.
Trying to do a 'make xconfig' fails with:
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
CHECK qt
*
* Unable to find the QT installation. Please make sure that
* the QT development package is correctly installed and
* either install pkg-config or set the QTDIR environment
* variable to the correct location.
*
HOSTCC scripts/kconfig/conf.o
sed < scripts/kconfig/lkc_proto.h > scripts/kconfig/lkc_defs.h
's/P(\([^,]*\),.*/#define \1 (\*\1_p)/'
HOSTCC scripts/kconfig/kconfig_load.o
HOSTCC scripts/kconfig/kxgettext.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
make[1]: *** No rule to make target `scripts/kconfig/.tmp_qtcheck',
needed by `scripts/kconfig/qconf.o'. Stop.
make: *** [xconfig] Error 2
Is this a problem with my setup or that kbuild/kconfig can't handle Qt4?
I noticed that scripts/kconfig/Makefile checks for:
pkg-config --exists qt
pkg-config --exists qt-mt
whereas the Qt4 installation I have the *.pc files are:
Qt3Support.pc
QtCore.pc
QtGui.pc
and also the places where kconfig checks for qconfig.h doesn't seem to
be where Qt4 keeps it (in my installation),
/usr/share/qt4/include/QtCore/qconfig.h
/usr/share/qt4/include/Qt/qconfig.h
Anyone else run into the same problem?
-jb
--
Tact is the art of making a point without making an enemy.
next reply other threads:[~2007-06-23 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 18:44 jimmy bahuleyan [this message]
2007-06-23 22:13 ` make xconfig failure on 2.6.21.5 Sam Ravnborg
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=467D6A21.8020507@gmail.com \
--to=knight.camelot@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).