to have the
filename "Makefile" hard-coded everywhere. Can this be fixed easily?
Is there a reason why the filename is restricted?
--
Timur Tabi
Staff Software Engineer
[EMAIL PROTECTED]
---
This SF.Net email is sponsored by BEA Webl
I'm
using Suse Linux 9.1 Pro. I have a suspicion that Suse's using an old
version of kbuild.
--
Timur Tabi
Staff Software Engineer
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT product
make. I know I could make
it more intelligent, but that's not the point. The point is that I
can't get O= to work, and I'd like to know why.
I'm using kernel version 2.6.5-52, as shipped with Suse Enterprise Linux 9.
--
Timur Tabi
Staff
ve one kernel source tree that's been mounted read-only and that all
developers share. With kbuild, each developer needs to have write
access to the source tree because a whole bunch of stuff (I have no idea
what) is written to the source tree, even when compiling an external
module. Th
Sam Ravnborg wrote:
Today it is not possible to tell kbuild to store output files
in a different directory when building external modules.
So for an external module located in .../external/foo output files
for the module will be stored in ../external/foo no matter usage of O=
I understand that now,
