Re: Error using "make KBUILD_OUTPUT=path" or "make O=path"

[Adrian Bunk]

On Fri, Apr 11, 2008 at 02:38:29PM +0200, Antonio Ãvila wrote:
> First of all, I'd like to introduce myself, my name is Anthony and
> I've been using linux during the last 8 years.
> I have googled around and I haven't found anything so let's go to the question:
>  It seems that when initializing either KBUILD_OUTPUT or O variables
> (make KBUILD_OUTPUT="../build/" ) there is a problem, the output is
> effectivly working, but the problem is that some files (.config) that
> has been generated at the begining of the make process, are later used
> and as a  consecuence, the make is trying to read them as the file was
> created in the base path instead of $KBUILD_OUTPUT...
> 
> Or maybe I'm completely wrong about the using of that variables... :)
> I've attached an output log of the error.
> 
> More info:
> - The kernel has been configured
> - If I omit the O= or KBUILD_OUTPUT= initializations the kernel
> compiles wonderfull.
>...

You also have to give the O= to the make commandline when configuring 
the kernel - this will put the .config to the right place.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/