<br><div class="gmail_quote">On Wed, Jun 30, 2010 at 1:09 AM, Brian Pitts <span dir="ltr"><<a href="mailto:brian@polibyte.com">brian@polibyte.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 06/29/2010 09:45 PM, Marc Ferguson wrote:<br>
</div><div class="im">> And that's where you fine folks come into play. The details of my issue<br>
> is on their site, but I don't think I understand how the Makefiles and<br>
> autorun.sh files play together. There seems to be a Makefile in the root<br>
> directory and another one in the "src" directory. The one in root is<br>
> being executed (I think), but it's not creating the 3 simple directories<br>
> it's supposed to create. The error I'm getting makes me believe that the<br>
> second Makefile isn't be executed at all. Can someone shed some light on<br>
> this issue? Thanks.<br>
<br>
</div>A few things based on your comment on google code.<br>
<br>
First, the '-C' argument to 'make' means "change to this directory<br>
before looking for the makefile or anything else". Based on your comment<br>
on google code, I think you misunderstood this to mean "create a directory"<br>
<br>
Second, when you touch the ko file it goes away after you run autorun.sh<br>
because 'make clean' completed successfully.<br>
<br>
Third, the ko file isn't created because 'make modules' failed.<br>
<br>
You my be saying "huh, make clean? make modules?" right about now, so<br>
lets walk through things.<br>
<br>
I've extracted the archive to ~/r8168-8.018.00.<br>
<br>
I see autorun.sh line 24 runs 'make all', which will run make using<br>
~/r8168-8.018.00/Makefile.<br>
<br>
The 'all' target really makes three other targets. Each of these targets<br>
is simply a call to a target of another makefile, the one at<br>
~/r8168-8.018.00/src/Makefile.<br>
<br>
In ~/r8168-8.018.00/src/Makefile you see the commands that are run for<br>
the 'clean' and 'install' targets. However, the 'modules' target runs<br>
make yet again with another makefile, /lib/modules/$(uname<br>
-r)/build/Makefile.<br>
<br>
Almost certainly Jim's answer earlier answer is the right one. I can<br>
build the module without any trouble. You could try switching to the src<br>
directory , running 'make modules', and seeing what errors you get.<br>
<br>
If you want to learn more about make, maybe this is a good starting place<br>
<br>
<a href="http://www.gnu.org/software/make/manual/make.html#Introduction" target="_blank">http://www.gnu.org/software/make/manual/make.html#Introduction</a><br>
<div><div></div><div class="h5"><br>
--<br>
All the best,<br>
Brian Pitts<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br>Thanks fellas for the excellent suggestions. It's funny that "kernel-devel" and "gcc" don't come preinstalled in the Live version. It probably would have made this process a whole lot easier. Since I am working offline I'll try and get the RPMs onto a USB key. My other box is Windows.<br clear="all">
<br>-- <br>Marc Ferguson<br><br>Registered Linux User #410978<br><a href="http://www.fergytech.com">www.fergytech.com</a> | <a href="http://www.digitalalias.net">www.digitalalias.net</a><br><br>"When life gives me lemons... I make Linuxaide, hmm good stuff!"<br>