Matt Housh wrote:
On Tue, 2007-05-08 at 13:59 -0500, Chris Pemberton wrote: [...]
Here is the error:
... make[1]: Entering directory `/usr/src/linux-2.6.20.3' /usr/src/linux-2.6.20.3/Makefile:491: /usr/src/linux-2.6.20.3/arch//Makefile: No such file or directory
[...]
That bit looks pretty suspicious; /usr/src/linux-2.6.20.3/arch/<arch>/Makefile would be more useful, such as /usr/src/linux-2.6.20.3/arch/i386/Makefile. Not sure why the arch wouldn't be set properly, though.
Matt (jaeger@freenode/#crux)
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
Well, I "solved" the problem. I compiled /usr/ports/opt/alsa-driver on the desktop machine (PIII i686). Transferred the modules from the desktop to the laptop (core2). When laptop tried to load the modules, it complained horribly about not having core2 built into them. And that got me thinking.... I rebuilt the laptop kernel and changed it to PIII i686 instead of Core2. Rebooted laptop. This time laptop /usr/ports/opt/alsa-driver compiled clean! So, I'm off to the kernel and alsa mailing lists to report the bug. Who would have thought selecting core2 in the kernel would screw up the external alsa drivers? Chris