All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: linux-kernel@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Check handling of kernel build output directory
Date: Fri, 26 Oct 2007 20:40:22 +0200	[thread overview]
Message-ID: <fftcal$dim$1@ger.gmane.org> (raw)
In-Reply-To: <19f34abd0710261036m65fd0d3bjace68c860a29023b@mail.gmail.com>

> Aren't you supposed to use O= as described by "make help"?

I expect that both ways should work. I find it easier to use the environment variable
"KBUILD_OUTPUT" because the command line parameter does not need to be repeated on each
make invocation.

Anyway - How do you think about my following test result?

Sonne:/usr/src/linux # MY_OUTDIR=/usr/src/obj/linux/2.6.23.1/x86_64/adjusted && rm -rf
$MY_OUTDIR/*
Sonne:/usr/src/linux # unset KBUILD_OUTPUT && make mrproper
  CLEAN   .config
Sonne:/usr/src/linux # cp -p /boot/config-2.6.23.1-0-adjusted .config
Sonne:/usr/src/linux # make O=$MY_OUTDIR oldconfig && date && echo
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX && make -j3 O=$MY_OUTDIR && echo
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY && make -j3 O=$MY_OUTDIR modules_install install
&& echo ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ && date
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/docproc
  GEN     /usr/src/obj/linux/2.6.23.1/x86_64/adjusted/Makefile
  HOSTCC  scripts/kconfig/conf.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
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf -o arch/x86_64/Kconfig
*
* Linux Kernel Configuration
*
[...]
#
# configuration written to .config
#
Fri Oct 26 20:30:39 CEST 2007
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  GEN     /usr/src/obj/linux/2.6.23.1/x86_64/adjusted/Makefile
scripts/kconfig/conf -s arch/x86_64/Kconfig
  GEN     /usr/src/obj/linux/2.6.23.1/x86_64/adjusted/Makefile
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  CHK     include/linux/utsrelease.h
  UPD     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86_64
  Using /usr/src/linux-2.6.23.1 as source for kernel
  /usr/src/linux-2.6.23.1 is not clean, please run 'make mrproper'
  in the '/usr/src/linux-2.6.23.1' directory.
make[1]: *** [prepare3] Error 1
make: *** [_all] Error 2
make: INTERNAL: Exiting with 4 jobserver tokens available; should be 3!

How does any internal status information get inconsistent here?

Regards,
Markus


  reply	other threads:[~2007-10-26 18:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 17:31 Check handling of kernel build output directory Markus Elfring
2007-10-26 17:36 ` Vegard Nossum
2007-10-26 18:40   ` Markus Elfring [this message]
2007-10-26 19:05     ` Markus Elfring
2007-10-27 11:32       ` Jan Engelhardt
2007-10-27 12:21         ` Sam Ravnborg
2007-10-26 19:05 ` Sam Ravnborg
2007-10-26 19:25   ` Markus Elfring
2007-10-26 19:47     ` Sam Ravnborg
2007-10-27  5:07       ` Markus Elfring
2007-10-27  7:23         ` Sam Ravnborg
2007-10-27 12:30           ` Markus Elfring
2007-10-27 16:00           ` Markus Elfring
2007-10-27 11:33 ` Jan Engelhardt
2007-10-27 12:41   ` Markus Elfring

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='fftcal$dim$1@ger.gmane.org' \
    --to=markus.elfring@web.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.