From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org
Subject: Re: 2.6.18: qconf.moc does not get rebuilt in separate build directory
Date: Sat, 28 Oct 2006 11:29:38 +0400 [thread overview]
Message-ID: <200610281129.42881.arvidjaar@mail.ru> (raw)
In-Reply-To: <200610012134.53322.arvidjaar@mail.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 01 October 2006 21:34, Andrey Borzenkov wrote:
> I am not sure what happened; but at some point it refused to do xconfig.
> This is vanilla 2.6.18.
>
> {pts/1}% LC_ALL=C make -C $PWD O=$HOME/build/linux-2.6.18 V=1 xconfig
> make: Entering directory `/home/bor/src/linux-git'
> make -C /home/bor/build/linux-2.6.18 \
> KBUILD_SRC=/home/bor/src/linux-git \
> KBUILD_EXTMOD="" -f /home/bor/src/linux-git/Makefile xconfig
> make -f /home/bor/src/linux-git/scripts/Makefile.build obj=scripts/basic
> /bin/sh /home/bor/src/linux-git/scripts/mkmakefile \
> /home/bor/src/linux-git /home/bor/build/linux-2.6.18 2 6
> GEN /home/bor/build/linux-2.6.18/Makefile
> mkdir -p include/linux include/config
> make -f /home/bor/src/linux-git/scripts/Makefile.build obj=scripts/kconfig
> xconfig
>
> g++ -Wp,-MD,scripts/kconfig/.qconf.o.d -Iscripts/kconfig -O2 -DQT_SHARED
> -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -D_REENTRANT -I/usr/lib/qt3//include -D
> LKC_DIRECT_LINK -c -o
> scripts/kconfig/qconf.o /home/bor/src/linux-git/scripts/kconfig/qconf.cc
> /home/bor/src/linux-git/scripts/kconfig/qconf.cc:30:21: error: qconf.moc:
> No such file or directory
> make[2]: *** [scripts/kconfig/qconf.o] Error 1
> make[1]: *** [xconfig] Error 2
> make: *** [xconfig] Error 2
> make: Leaving directory `/home/bor/src/linux-git'
>
> {pts/1}% make --version
> GNU Make 3.81
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
>
> This program built for i586-mandriva-linux-gnu
>
Still the same problem with 2.6.18.1
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFQwbmR6LMutpd94wRArDfAKCvwPioBz2uDsNY1hTlZviJvxSgrACfe0yW
w4S7IaMzIfc1YrwFEfOif3U=
=QzN5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-10-28 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 17:34 2.6.18: qconf.moc does not get rebuilt in separate build directory Andrey Borzenkov
2006-10-28 7:29 ` Andrey Borzenkov [this message]
2006-10-28 11:46 ` 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=200610281129.42881.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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