On Sat, Jan 29, 2005 at 12:41:21PM -0600, Matt Domsch wrote:
> On Sat, Jan 29, 2005 at 03:40:06PM +0100, Sam Ravnborg wrote:
> > What is missing in the above is when kbuild read in symbols from
> > Module.symvers I sideeffect of reading in Module.symvers is also
> > that modpost gets enough dependency information to build the depends
> > line correct.
> >
> > So if you make sure not to delete Module.symvers in the kernel you
> > point at with -C ... then you should see dependency being generated
> > correct. I'm about to merge a patch from Andreas G that add a
> > warning if Module.symvers is missing when supposed to be present.
>
> Ahh, ok, that explains a lot. It's likely that in Paul's original
> problem, the cross-compile situation, the copy of Module.symvers being
> used was from the wrong arch (another case where
> /lib/modules/... isn't arch-aware), or not present.
For running version of kernel:
/lib/modules/`uname -r`/build/Module.symvers should be correct.
If not the kernel has been installed in the wrong way.
For cross compile situation one has to point to the dir where
the kernel is being build, and not /lib/modules/... assuming that
the kernel is build for another machine.
Sam
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
kbuild-devel mailing list
kbuild-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
