lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 11 Apr 2008 14:38:29 +0200
From:	"Antonio Ávila" <aavilagallego@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Error using "make KBUILD_OUTPUT=path" or "make O=path"

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.

"Thanks a log" and please don't forget to add my address to the CC
since I'm not subscribed to the list.

Download attachment "output.log" of type "application/octet-stream" (2685 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ