Re: Check handling of kernel build output directory

2007-10-27 Thread Markus Elfring
>> Which files are not clean in my situation after the command "make mrproper" >> was executed >> at the beginning? > If you look at the top-level Makefile you will see: > > @echo ' Using $(srctree) as source for kernel' > $(Q)if [ -f $(srctree)/.config -o -d $(srctree)/include/c

Re: Check handling of kernel build output directory

2007-10-27 Thread Markus Elfring
> .config should be copied to the output directory. This copy will usually happen by a command like "make O=/usr/src/obj/linux/2.6.23.1/x86_64/adjusted silentoldconfig". It seems that something runs unusual on my openSUSE 10.3 system when an extra output directory was specified. Regards, Markus

Re: Check handling of kernel build output directory

2007-10-27 Thread Markus Elfring
> From the above we can see that two make's are running in parallel here > where only one should run. Is this a problem here? - I can omit the parameter "-j". > I have seen this before but only in cases where you specified several targets > on the make commandline - which you do not do in the ma

Re: Check handling of kernel build output directory

2007-10-27 Thread Sam Ravnborg
On Sat, Oct 27, 2007 at 01:32:54PM +0200, Jan Engelhardt wrote: > > On Oct 26 2007 21:05, Markus Elfring wrote: > >>> 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_OUTPU

Re: Check handling of kernel build output directory

2007-10-27 Thread Jan Engelhardt
On Oct 26 2007 21:05, Markus Elfring wrote: >>> 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

Re: Check handling of kernel build output directory

2007-10-27 Thread Jan Engelhardt
On Oct 26 2007 19:31, Markus Elfring wrote: > >Two ways are mentioned in the Makefile for the Linux kernel 2.6.31.1 to >specify output >diretories. The description of the environment variable "KBUILD_OUTPUT" is >missing from >the file "README". > >I am trying to generate all executable files for

Re: Check handling of kernel build output directory

2007-10-27 Thread Sam Ravnborg
Hi Markus. Please do not edit cc: and to: - it is easy to miss out a mail on lkml. On Sat, Oct 27, 2007 at 07:07:55AM +0200, Markus Elfring wrote: > > You did it in your output directory I assume. > > No. > > > > kbuild complains that the source directory is not clean - which > > is what you n

Re: Check handling of kernel build output directory

2007-10-26 Thread Markus Elfring
> You did it in your output directory I assume. No. > kbuild complains that the source directory is not clean - which > is what you need to clean up. I am looking for the real reasons for the occuring error messages. Let us look at another test example ... Sonne:~ # ls -ld /usr/src/linux lrwx

Re: Check handling of kernel build output directory

2007-10-26 Thread Sam Ravnborg
> > I did that clean-up step. You did it in your output directory I assume. kbuild complains that the source directory is not clean - which is what you need to clean up. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTE

Re: Check handling of kernel build output directory

2007-10-26 Thread Markus Elfring
> So here you do not have a .config file in the directory: > /usr/src/obj/linux/2.6.23.1/x86_64/adjusted > So you are told to create one using some of the available methods. The README contains the following description. "... "make oldconfig" Default all questions based on the contents

Re: Check handling of kernel build output directory

2007-10-26 Thread Markus Elfring
>> 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. A wording correction: I expect

Re: Check handling of kernel build output directory

2007-10-26 Thread Sam Ravnborg
Hi Markus. > Two ways are mentioned in the Makefile for the Linux kernel 2.6.31.1 to > specify output > diretories. The description of the environment variable "KBUILD_OUTPUT" is > missing from > the file "README". It is on purpose left out - README contains only the most typical stuff. And no-

Re: Check handling of kernel build output directory

2007-10-26 Thread Markus Elfring
> 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 followin

Re: Check handling of kernel build output directory

2007-10-26 Thread Vegard Nossum
On 10/26/07, Markus Elfring <[EMAIL PROTECTED]> wrote: > Hello, > > Two ways are mentioned in the Makefile for the Linux kernel 2.6.31.1 to > specify output > diretories. The description of the environment variable "KBUILD_OUTPUT" is > missing from > the file "README". Aren't you supposed to use

Check handling of kernel build output directory

2007-10-26 Thread Markus Elfring
Hello, Two ways are mentioned in the Makefile for the Linux kernel 2.6.31.1 to specify output diretories. The description of the environment variable "KBUILD_OUTPUT" is missing from the file "README". I am trying to generate all executable files for the current stable kernel release on my open