Messages in this thread |  | | From | Keith Owens <> | Subject | Re: test10-pre7 | Date | Tue, 31 Oct 2000 09:06:20 +1100 |
| |
On Mon, 30 Oct 2000 17:01:20 -0500, Jeff Garzik <jgarzik@mandrakesoft.com> wrote: >Keith Owens wrote: >> USB still gets unresolved symbols when part is in kernel, part is in >> modules and modversions are set. Patch against 2.4.0-test10-pre7, only >> affects drivers/usb/Makefile. > >Or instead of all that, you could simply call the core init function >from init/main.c...
Does that work when all of usb is a module? The point of __initcall is to avoid all the conditional code that used to be in main.c.
>Ya know, sorting those lists causes this problem, too... usb.o is >listed first in the various lists, as is usbcore.o. Is it possible to >avoid sorting? Doing so will fix this, and also any other link order >breakage like this that exists, too.
You have it backwards. Rules.make does *not* sort, the link order is implicit in the declaration order of objects in the Makefiles. For most makefiles, this kludge works, it does not work for USB. See http://www.uwsg.indiana.edu/hypermail/linux/kernel/0010.3/0661.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |