Hi. I had a question about the Kbuild machinery which isn’t answered in the documentation. In the example in section 3, we have: 8123_if.c 8123_if.h 8123_pci.c 8123_bin.o_shipped <= Binary blob but what if we were dealing with someone who had written a 2.4 Makefile, and had named the files: 8123.c <= problematic name 8123_if.c 8123_if.h 8123_pci.c 8123_bin.o_shipped instead? It seems to me that the line: 8123-y := 8123.o 8123_if.o 8123_pci.o 8123_bin.o would be problematic (i.e. a circular dependency). Yes, the person who developed the software I’m trying to Build should probably have named 8123.c as “8123_main.c” instead, but he didn’t... though arguably it’s an unnecessary restriction to not have a source file called $(module_name).c in the list of sources for $(module_name).ko ... So how does one work around this issue? A possible fix to the Kbuild machinery itself would involve linking the $(8123-y) object files into 8123_.o instead, and then using that to derive 8123.ko ... Thanks, -Philip -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
