From: "Joseph D. Wagner" <wagnerjd@prodigy.net>
To: 'Chuck Winters' <cwinters@atl.lmco.com>,
linux-c-programming@vger.kernel.org
Subject: RE: config.h
Date: Wed, 11 Dec 2002 01:28:42 -0600 [thread overview]
Message-ID: <001d01c2a0e6$ef85a2b0$972a3a41@joe> (raw)
In-Reply-To: <20021210155618.A11637@atl.lmco.com>
> Would it be prudent to include the linux/config.h
> file in a user level program to check for the
> existence of certain modules? I know there are
> other ways, like using autoconf, etc. I was just wondering.
No, because modules can be dynamically loaded on-the-fly, completely
independent of however the kernel is compiled.
Additionally, config.h (actually just an #include for autoconfig.h) is an
automatically generated file which varies depending upon how an INDIVIDUAL
USER compiles his/her own INDIVIDUAL kernel. There's no way for you to
anticipate the contents of config.h in advance. It's better to use other
methods.
Use of config.h would be necessary if you were compiling something directly
into the kernel.
Joseph Wagner
prev parent reply other threads:[~2002-12-11 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 20:56 config.h Chuck Winters
2002-12-11 7:28 ` Joseph D. Wagner [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='001d01c2a0e6$ef85a2b0$972a3a41@joe' \
--to=wagnerjd@prodigy.net \
--cc=cwinters@atl.lmco.com \
--cc=linux-c-programming@vger.kernel.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).