Re: kernel compile problem -- unresolved symbols
I'm compiling for a K7/Athlon/Duron system. As far as I can tell, -all-
modules come up with unresolved symbols. In other words, any module I try to
load comes up with unresolved symbols, whether part of the kernel, or
standalone. Clearly, I am doing something very wrong, though I haven't
changed the methods for compiling, that have worked successfully for me since
about 2.4.13. I have made sure (to the best of my knowledge) that I have
sufficiently new versions of the important packages.
modutils 2.4.13-3
debhelper 3.4.11
kernel-package 7.93
Also sprach Faheem Mitha:
> On 11 Mar 2002, Christopher M. Jones wrote:
> > I am having a problem compiling from source 2.4.17 packaged for Debian.
> > Using make-kpkg kernel_image in the source dir, all my modules come up
> > with unresolved symbols.
> >
> > What causes this? What am I doing wrong? What should I do to fix it?
> > Using gcc 2.95.4
>
> I've compiled 2.4.17 on a number of different machines with
> signicantly different hardware. I've never had a problem with
> unresolved symbols. However, I have not compiled many different
> stand-alone module packages. I think we need rather more information
> before we can help.
>
> Firstly, please tell us what modules are coming up with unresolved
> symbols, and then (optionally) show us what the unresolved symbols
> are. (These won't mean much to me but might to someone.) Are these
> modules part of a standalone package or part of the kernel? If the
> latter, unresolved symbols probably means you are doing something
> wrong.
>
> A word about your computer's hardware if relevant (like if the modules
> are drivers for hardware) might be helpful.
>
> Please remember there are no mindreaders on this list.
>
> Sincerely, Faheem Mitha.
Reply to: