On Fri, 2006-08-25 at 11:11 +0200, Jan Engelhardt wrote: > That's what I meant. Assume I explicitly built read.o foo.o and bar.o. > If I then run the regular make, it will rerun gcc for read.c foo.c and > bar.c rather than using the already-created .o files for linking. Yes. Just as if I run 'make fs/ntfs/inode.o' and then build my kernel, my build of fs/ntfs/inode.o isn't used -- because I don't have CONFIG_NTFS set. You built something manually that wasn't needed, and then it wasn't used. Is there a problem here? -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- From: Jan Engelhardt <[email protected]>
- Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- References:
- [PATCH 0/4] Compile kernel with -fwhole-program --combine
- From: David Woodhouse <[email protected]>
- Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- From: Jan Engelhardt <[email protected]>
- Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- From: David Woodhouse <[email protected]>
- Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- From: Jan Engelhardt <[email protected]>
- Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- From: David Woodhouse <[email protected]>
- Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- From: Jan Engelhardt <[email protected]>
- [PATCH 0/4] Compile kernel with -fwhole-program --combine
- Prev by Date: Re: [PATCH 2/4] Core support for --combine -fwhole-program
- Next by Date: Re: memory hotplug - looking for good place for cpuset hook
- Previous by thread: Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- Next by thread: Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
- Index(es):
 |