Wes Smith asks:
> It seems wrong to me that the .o is left in a different position based
> on whether it has exported symbols or not. Was this just an oversight,
> and no one has ever happened to have a subdirectory in their module
> directory, or is there some reason that Rules.make is written t
On Wed, 10 Apr 2002 11:13:14 -0700,
Wesley Smith <[EMAIL PROTECTED]> wrote:
>In the Rules.make file in both 2.4.18 and 2.5.7 kernels, the rule to
>make a .c into a .o looks like this:
>
>%.o: %.c
> $(CC) $(CFLAGS) [stuff deleted] -c -o $@ $<
>
>The rule to build a .c into .o when the .o ha
In the Rules.make file in both 2.4.18 and 2.5.7 kernels, the rule to
make a .c into a .o looks like this:
%.o: %.c
$(CC) $(CFLAGS) [stuff deleted] -c -o $@ $<
The rule to build a .c into .o when the .o happens to be in
$(export-objs) looks like this:
$(export-objs): $(export-objs:.o=.c
