Re: MOL Modules Compilation weirdness
Just wanted to say thanks for your advice. Even
though I kept my current kernel source in
/usr/src/linux, your e-mail did provide me a clue
with what was wrong. Turns out the files in
/usr/include/linux were messed up on my machine. I
blame it on the poor upgrade from the Woody CD-ROM.
I re-installed the glibc headers and now I
correctly compiled the modules and mol recognizes
them as belonging to my current kernel.
mean while getting mol to actually run is my next
problem, see my next post.
Thanks for your help,
W. Crowshaw
On Sun, Nov 24, 2002 at 05:54:45PM -0500, Albert D. Cahalan wrote:
> The usual junk: some people mistakenly think that /usr/include/linux
> is supposed to contain a link into /usr/src/linux and that that is
> supposed to be source code for the kernel you are running.
>
> Reality:
>
> The /usr/include/linux files are derived from kernel source when
> the glibc package is created. Don't touch them. They get upgraded
> when you upgrade glibc. Treat /usr/include/asm the same way.
>
> That's just the way it is. Linus said so. IMHO these files
> ought to be a separate package, but that isn't the case.
>
> You should not have a /usr/src/linux directory. You might put
> something there to help you avoid temptation:
>
> rm -rf /usr/src/linux
> echo "never use this" > /usr/src/linux
> chmod 444 /usr/src/linux
> chattr +i /usr/src/linux
>
> If you need kernel source, put it in your home directory.
>
> Now look in the MOL source. If you see /usr/src/linux or
> /usr/src/asm, then MOL is most likely broken. Fix it by
> adding a -I option to the gcc command line, by editing
> the source, or by doing both. You'll need to point MOL to
> the kernel source in your home directory.
>
>
> --
> To UNSUBSCRIBE, email to debian-powerpc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
--
wcrowshaw
Reply to: