From: miloody@gmail.com (loody)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Recompile the Library of the Linux Kernel
Date: Mon, 13 Feb 2012 17:22:05 +0800 [thread overview]
Message-ID: <CANudz+vE97SJXd0uvVdQvbKuMeJx2haJ__Mv8qLL69OeLZG8_g@mail.gmail.com> (raw)
In-Reply-To: <CADtdGo8zOh3=82eOJaSADfhoe-1OkSH9pgRpTc20y9Er9FmqBQ@mail.gmail.com>
hi:
2012/2/13 LI LEI <leimli.hit@gmail.com>:
> Hello, everyone,
>
> I am a beginner to learn about the linux kernel. I met the following problem
> today:
>
> I created a C file called "drv_event.c", and put it into the location
> "/lib", since I want to link it to the library of the kernel, i.e.,?lib.a. I
> also?put the header file "drv_event.h" into the directory "/include/linux".
> I recompile the directory "/lib", and my own object "drv_event.o" was
> successfully linked into the?lib.a.
>
> However, I called one of the functions defined in the "drv_event.c" in my
> driver, and I compiled this driver, at the link time, I got the warning
> which shows that the function called is undefined.
Would you please show us the warn message?
does your driver made in module format or build-in?
>
> It seems although I do recompile the lib.a successfully, but I did not put
> the new one into the right place. I tried "make install lib" and also "make
> install" in the kernel source. However, I still got the same warning at the
> link time.
>
> So does someone can help me to get rid of this problem?
>
> Thanks so much.
>
> Best,
>
> Li
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Regards,
prev parent reply other threads:[~2012-02-13 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 7:39 Recompile the Library of the Linux Kernel LI LEI
2012-02-13 9:22 ` loody [this message]
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=CANudz+vE97SJXd0uvVdQvbKuMeJx2haJ__Mv8qLL69OeLZG8_g@mail.gmail.com \
--to=miloody@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 NNTP newsgroup(s).