Messages in this thread | | | Date | Tue, 27 May 2003 06:48:25 +0200 | From | Sam Ravnborg <> | Subject | Re: 2.5.69-bk19 "make" messages much less informative |
| |
On Mon, May 26, 2003 at 03:23:05PM -0700, Adam J. Richter wrote: > Also, I used to be able to copy and paste the gcc command > for compiling a particular file when I'm trying to get rid of compiler > errors.
The easy way to handle this is actually to ask kbuild to compile the file in question. Example: $ make arch/i386/kernel/acpi/boot.o
This wil perfectly fine compile boot.c - no need to hassle with copying long gcc command lines.
A shorthand exists for compiling all built-in files in a directory as well. Very useful when working on a subsystem. Assuming ext2 is built-in try out: $ make fs/ext2/
And as already pointed out, the easy way to enable to verbose output is to use: $ make V=1
Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |