public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Georg Nikodym" <georgn@somanetworks.com>
To: linux-kernel@vger.kernel.org
Cc: georgn@somanetworks.com, greg@wind.enjellic.com, sct@dcs.ed.ac.uk
Subject: linux-2.4.0-test11 and sysklogd-1.3-31
Date: Wed, 6 Dec 2000 17:24:58 -0500 (EST)	[thread overview]
Message-ID: <14894.48314.363938.770481@somanetworks.com> (raw)


sysklogd 1.3-31 no longer compiles using the latest headers in test11.

Strictly speaking this isn't a kernel bug...

sysklogd's ksym_mod.c includes <linux/module.h>

In test11, <linux/module.h> added struct inter_module_entry.  Its
first member is "struct list_head list;".  This necessitates the
inclusion of <linux/list.h>.

The trouble is that <linux/list.h> is almost completely protected by
#ifdef __KERNEL__.

sysklogd, obviously, doesn't compile with __KERNEL__ so the struct
inter_module_entry declaration is impossible and the compilation
fails.

It's not clear to me who's code needs changing so I'm sending both to
linux-kernel and to some of the people that have the misfortune of
being listed on the sysklogd man page.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-06 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 22:24 Georg Nikodym [this message]
2000-12-06 23:46 ` linux-2.4.0-test11 and sysklogd-1.3-31 Keith Owens
2000-12-07 17:36   ` Georg Nikodym
2000-12-07 22:51     ` Keith Owens
2000-12-08 16:30       ` Georg Nikodym
2000-12-08 22:16         ` Keith Owens
2000-12-12  1:13           ` Georg Nikodym
2000-12-12  1:29             ` Georg Nikodym
2000-12-12  1:30             ` Keith Owens
2000-12-12  1:53               ` Georg Nikodym
2000-12-12  3:57                 ` Peter Samuelson

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=14894.48314.363938.770481@somanetworks.com \
    --to=georgn@somanetworks.com \
    --cc=greg@wind.enjellic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@dcs.ed.ac.uk \
    /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