kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: link question
Date: Thu, 30 Jun 2011 00:46:19 +0700	[thread overview]
Message-ID: <BANLkTin0KNbyD_ECk8tfGkscDKCmtzQ1RA@mail.gmail.com> (raw)
In-Reply-To: <4E0B629E.6030302@tysdomain.com>

Hi...

On Thu, Jun 30, 2011 at 00:36, Littlefield, Tyler <tyler@tysdomain.com> wrote:
> I have a quick question; this is something I haven't been able to figure
> out. By using the kernel headers you can call functions that are defined
> in the kernel, but you don't actually have to link to the kernel or any
> sort of library. How does this work? How does compiled code call the
> function if it doesn't link to it in some way or another?.

you need to look closer....for example include/linux/mm.h. There you
will see definition of constants and functions used for memory
management.

So, what library here means IMHO are group of headers that contains
the needed functions/definitions by themselves. Linking? I think it's
better named as "including"...indeed there are linking process during
kernel build, but that is just a way to build final image using
several objects which originated from the practice of refactoring etc.

kindly CMIIW people...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

  reply	other threads:[~2011-06-29 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 17:36 link question Littlefield, Tyler
2011-06-29 17:46 ` Mulyadi Santosa [this message]
2011-06-29 17:56   ` Littlefield, Tyler
2011-06-29 18:40 ` Greg KH
2011-06-29 20:05   ` Guillaume Knispel
2011-06-29 21:10 ` 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=BANLkTin0KNbyD_ECk8tfGkscDKCmtzQ1RA@mail.gmail.com \
    --to=mulyadi.santosa@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).