From owner-freebsd-hackers  Mon Jul  6 12:06:13 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA00364
          for freebsd-hackers-outgoing; Mon, 6 Jul 1998 12:06:13 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from digi.digiware.nl (gtw.digiware.nl [194.151.72.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00288
          for <hackers@FreeBSD.org>; Mon, 6 Jul 1998 12:05:55 -0700 (PDT)
          (envelope-from wjw@digi.digiware.nl)
Received: by digi.digiware.nl (8.8.7/1.63)
    id TAA16622; Mon, 6 Jul 1998 19:03:44 GMT
From: wjw@digi.digiware.nl (Willem Jan Withagen)
Message-Id: <199807061903.TAA16622@digi.digiware.nl>
Subject: Re: adding to sysctl env.
In-Reply-To: <199807060646.XAA21779@usr02.primenet.com> from Terry Lambert at "Jul 6, 98 06:46:20 am"
To: tlambert@primenet.com (Terry Lambert)
Date: Mon, 6 Jul 1998 21:03:43 +0200 (CEST)
Cc: wjw@digiware.nl, mike@smith.net.au, terry@lambert.org, hackers@FreeBSD.ORG
Reply-To: wjw@digiware.nl
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

=>  > Reason I ask, is that there were no errors when I compiled without
=>  > the inclusion, but that was the problem I could not see the 
=>  > debug.vlinkxlate in sysctl. :-(
=>  
=>  You need to look into why there were no errors.  At a minimum, there
=>  should have been a linktime error, if a macro was confused as an external
=>  function reference.

That's why I was suprised as well. I found out about the problem by
compiling the module with 'cc -E' checking what cpp made of it.
It just left the TEXT_SET in plain tekst there.

So I suppose that there is a TEXT_SET to be linked against which doesn't
harm the code. :-(

=>  The man page is useful, but the inclusion of the kernel.h was probably
=>  for some other prototype, not the sysctl prototype, IMO.  You need to
=>  narrow down your problem to make sure you aren't documenting an #include
=>  that is necessary for your implementation, and not for sysctl's in
=>  general.

I'll undo the fix, and see what comes of it. Currently my kernel has 
not *TEXT_* items.

--WjW


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message