Brian Nelson wrote: > That's an upstream kernel source problem, which I think is supposed to > be fixed in 2.4.17.
It isn't, at least not completely. There have been several reports on this list of people failing to build 2.4.17 with similar errors. The problem appears to be highly dependent on the kernel configuration, so some people will have problems, while others won't. The answer, for now, is to downgrade to binutils 2.11.92.0.10-4, the last version that reliably worked with recent kernel sources. It can be downloaded from my archive of not-quite-latest Debian Sid packages (which should be accessed with a web browser, not apt/dselect/dpkg, because it isn't a proper package repository, just a directory full of .deb files): http://crdic.ath.cx/debian/ I notice today there was a new binutils package in Sid. Whether it works with recent kernels or not, I do not know, as I have binutils locked at 2.11.92.0.10-4 until I have a good reason to upgrade it. > Also, it's usually advisable to use the debian kernel packages rather > than the kernel.org sources. I see no reason to prefer the debian-packaged kernel sources. They usually differ only in very minor ways, adding a few patches for bug fixes. I always wonder why these patches aren't in the official kernel sources. Maybe because they haven't been tested enough yet, or because the official kernel maintainer doesn't think they're the right solution? Craig
