From: Jim Cromie <jim.cromie@gmail.com>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: Balachandar <bala1486@gmail.com>,
kernelnewbies@nl.linux.org, linux-c-programming@vger.kernel.org
Subject: Re: Error in compiling a module
Date: Thu, 29 Jul 2010 12:10:23 -0600 [thread overview]
Message-ID: <AANLkTinRJQM+Yky_ORVnf3i7Aq2CiUTvchQDxiR4D636@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimeJrRs4Bd1aw--FKPYyqcuu8_O-Xi5G0FOh0yd@mail.gmail.com>
On Wed, Jul 28, 2010 at 10:51 PM, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> Hi...
>
> On Thu, Jul 29, 2010 at 00:28, Balachandar <bala1486@gmail.com> wrote:
>> Thank you for your help. I figured out the mistake. I missed a
>> semicolon in one of the header file that was included in the file that
>> showed the error.
>
> I think it would be great if you and some guys here write about
> "mistakes I ever did when I write kernel codes" in kernelnewbies
> wiki....so that others might learn about it.
>
> Just 2 cents suggestion...
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
Hi Mulyadi,
Youre a regular here, and would have some "authority" on making recommendations.
The trouble I have with "edit the wiki" suggestions is that people
get intimidated by questions of "where to put stuff ?".
I just looked at HelpforBeginners
http://kernelnewbies.org/HelpForBeginners
and encountered this:
You are encouraged to edit the WikiSandBox whichever way you like.
Please restrain yourself from editing other pages until you feel at
home with the ways a wiki works.
The unintended message I got from this is "dont touch the other stuff",
which doesnt set the bar low enough to encourage contributions -
it implies that "judges" might not like your content or its placement.
my $.02 - perhaps we need a CatchAll bucket for content that could be useful,
but contributor doesnt know where to put it. Organization could come
afterwards.
You cant sort a deck of cards until youve got the cards, and once you
do, its trivial
to determine that the 10-of-Spades is missing.
The bit Id add, in response to the now solved problem, would be:
Try making the *.i file to trace down whats missing (or not missing)
make -C /home/jimc/lx/linux-2.6.git O=/home/jimc/lx/sk/. drivers/hwmon/pc87360.i
Using /home/jimc/lx/linux-2.6.git as source for kernel
....
CPP [M] drivers/hwmon/pc87360.i
wrt Victor's post, my impression was that the real error was not spaces/tabs
but lack of linkage to the src tree...
$> make O=../<mybuilddir> defconfig
will write a new Makefile into the build dir, so you can make further
from there,
ie copy in an old .config, then make oldconfig to update it per latest source.
[jimc@harpo sk]$ make
make -C /home/jimc/lx/linux-2.6.git O=/home/jimc/lx/sk/.
Using /home/jimc/lx/linux-2.6.git as source for kernel
GEN /home/jimc/lx/sk/Makefile
CHK include/linux/version.h
His hint is useful and valuable in the right place, but I dont know
where that is
at this point, and I suspect many potential contributors would appreciate
more specific guidance, or a default place that can be organized once it
gets some content.
thanks
next prev parent reply other threads:[~2010-07-29 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:17 Error in compiling a module Balachandar
2010-07-27 22:30 ` Michal Nazarewicz
2010-07-28 4:59 ` Mulyadi Santosa
2010-07-28 17:28 ` Balachandar
2010-07-29 4:51 ` Mulyadi Santosa
2010-07-29 13:56 ` Victor Rodriguez
2010-07-29 13:56 ` Victor Rodriguez
2010-07-29 16:21 ` Michal Nazarewicz
2010-07-29 17:52 ` Mulyadi Santosa
2010-07-29 18:10 ` Jim Cromie [this message]
2010-07-29 20:23 ` Mulyadi Santosa
2010-07-29 20:35 ` Greg Freemyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTinRJQM+Yky_ORVnf3i7Aq2CiUTvchQDxiR4D636@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=bala1486@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-c-programming@vger.kernel.org \
--cc=mulyadi.santosa@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).