From: Bob Billson <reb@bhive.dhs.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: lkc 1.2: make xmenu error
Date: Wed, 30 Oct 2002 17:38:43 -0500 [thread overview]
Message-ID: <20021030223843.GF4186@etain.bhive.dhs.org> (raw)
Hi Roman ...
I was trying out lkc v1.2 on 2.5.44. make xconfig coughs up the following
error:
[reb@etain]:~/kernel/linux-2.5.44$ make xconfig
make -f scripts/Makefile
make -f scripts/kconfig/Makefile scripts/kconfig/qconf
gcc -Wp,-MD,scripts/kconfig/.conf.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o scripts/kconfig/conf.o scripts/kconfig/conf.c
gcc -Wp,-MD,scripts/kconfig/.kconfig_load.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o scripts/kconfig/kconfig_load.o scripts/kconfig/kconfig_load.c
gcc -Wp,-MD,scripts/kconfig/.mconf.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o scripts/kconfig/mconf.o scripts/kconfig/mconf.c
/usr/share/qt/bin/moc -i scripts/kconfig/qconf.h -o scripts/kconfig/qconf.moc
make[1]: /usr/share/qt/bin/moc: Command not found
make[1]: *** [scripts/kconfig/qconf.moc] Error 127
make: *** [scripts/kconfig/qconf] Error 2
This is on a Debian (testing tree) box with the libqt3-dev package
installed. moc is there, just not in /usr/share/qt/bin:
[reb@etain]:~/kernel/linux-2.5.44$ whereis moc
moc: /usr/bin/moc /usr/share/man/man1/moc.1.gz
I didn't see this mentioned on lkml yet. Apologies if it was and I missed
it.
bob
--
bob billson email: reb@bhive.dhs.org ham: kc2wz /)
reb@elbnet.com beekeeper -8|||}
"Níl aon tinteán mar do thinteán féin." --Dorothy Linux geek \)
[ GPG key: http://bhive.dhs.org/gpgkey.html ]
next reply other threads:[~2002-10-30 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 22:38 Bob Billson [this message]
2002-10-30 22:58 ` Roman Zippel
2002-10-31 3:36 ` Bob Billson
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=20021030223843.GF4186@etain.bhive.dhs.org \
--to=reb@bhive.dhs.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®