From: Michal Marek <mmarek@suse.cz>
To: John Kacur <jkacur@gmail.com>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Don't mkdir -p include/config in the sourcetree when using O=outputdir option
Date: Wed, 06 Jan 2010 21:45:25 +0100 [thread overview]
Message-ID: <4B44F665.6050008@suse.cz> (raw)
In-Reply-To: <520f0cf11001061210w4d33fca6y98f091c4260577c0@mail.gmail.com>
John Kacur napsal(a):
> Yes, I doubled checked that the problem exists, and it is quite easy for me to
> reproduce. However, my proposed solution is also broken, please don't
> apply, I'm still investigating.
>
> I am surprised that you are not able to reproduce the problem though.
> Did you follow the steps I that I outlined?
I did
$ git checkout v2.6.33-rc3
$ mkdir /bld/2.6.33-rc3
$ zcat /proc/config.gz >/bld/2.6.33-rc3/.config
$ make O=/bld/2.6.33-rc3/ oldconfig
...
hit Enter several times
...
$ ls -ld include/config /bld/2.6.33-rc3/include/config/
ls: cannot access include/config: No such file or directory
drwxr-xr-x 2 mmarek users 4096 2010-01-06 21:35
/bld/2.6.33-rc3/include/config//
$ make O=/bld/2.6.33-rc3/
GEN /bld/2.6.33-rc3/Makefile
scripts/kconfig/conf -s arch/x86/Kconfig
Using /home/mmarek/linux-2.6 as source for kernel
GEN /bld/2.6.33-rc3/Makefile
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
CC kernel/bounds.s
... continues building ...
The mkdir command has been in the Makefile since 2006 (c955cca), so I
think that your problem is caused by something else. Try a make V=1
build with a read-only source tree to see which mkdir command fails.
Michal
next prev parent reply other threads:[~2010-01-06 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 16:09 [PATCH] Don't mkdir -p include/config in the sourcetree when using O=outputdir option John Kacur
2010-01-06 19:34 ` Michal Marek
2010-01-06 20:10 ` John Kacur
2010-01-06 20:45 ` Michal Marek [this message]
2010-01-06 22:30 ` John Kacur
2010-01-06 22:33 ` John Kacur
2010-01-07 11:19 ` Michal Marek
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=4B44F665.6050008@suse.cz \
--to=mmarek@suse.cz \
--cc=jkacur@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--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