From owner-freebsd-current Mon Sep 28 13:31:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16557 for freebsd-current-outgoing; Mon, 28 Sep 1998 13:31:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16535 for ; Mon, 28 Sep 1998 13:31:10 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 2695 invoked by uid 1000); 28 Sep 1998 21:33:59 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809282007.OAA17623@panzer.plutotech.com> Date: Mon, 28 Sep 1998 17:33:59 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Kenneth D. Merry" Subject: Re: X11R6 and CAM (??) Cc: current@FreeBSD.ORG, garyj@muc.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry, On 28-Sep-98 you wrote: > Gary Jennejohn wrote... > > Simon Shapiro writes: > > >I know the ports are not dow yet, but this one does not seem ELF > > >related, > > >rather... CAM (??) releated; The following errors started cropping up > > >just > > >about when CAM was checked in. I searched for these symbols and > > >cannot > > >find them. Any clue? > > > > > >gcc -O2 -I. -I./lib/Xt -I. -I./X11 -I/usr/X11R6/include -I/include > > >-DCSRG_BASED -DHAVE_SYS_PARAM_H -DFUNCPROTO=15 -DNARROWPROTO -c > > >freebsd_system.c > > >freebsd_system.c:147: `DK_NDRIVE' undeclared here (not in a function) > > >freebsd_system.c:147: `DK_NAMELEN' undeclared here (not in a function) > > >freebsd_system.c:196: `DK_NDRIVE' undeclared here (not in a function) > > >freebsd_system.c: In function `total_disk_transfers': > > >freebsd_system.c:278: `DK_NDRIVE' undeclared (first use this function) > > >freebsd_system.c:278: (Each undeclared identifier is reported only > > >once > > >freebsd_system.c:278: for each function it appears in.) > > >freebsd_system.c: In function `collect_stats': > > >freebsd_system.c:310: `DK_NDRIVE' undeclared (first use this function) > > >freebsd_system.c:385: `MOUNT_NFS' undeclared (first use this function) > > >freebsd_system.c: In function `get_namelist': > > >freebsd_system.c:483: `DK_NDRIVE' undeclared (first use this function) > > >*** Error code 1 > > > > > > > since CAM this functionality is provided using sysctl. There's a > > library > > (libdevstat) which provides a pretty good interface and hides all the > > dirty details of using the sysctl's. > > > > This looks like xsysinfo. I munged it to work with libdevstat > > (basically > > stole the code from iostat :) and sent the changes to the maintainer. > > Unfortunately, he's currently doing his compulsory military service and > > doesn't have time to look at my changes :( > > Well, how about doing something like putting the devstat patches for it > in > the ports tree? That will probably do until the author has a chance to > merge the changes in. > > You might want to make the build procedure autodetect devstat, so it > will > work with either the 2.2.x releases or 3.0. I'd recommend doing > something > like: > > .if exists(/usr/include/devstat.h) > CFLAGS+= -DFREEBSD_DEVSTAT > .endif > > Or something like that. > > [ I would do it myself, but I'm extremely swamped at the moment..:( ] Sounds like a good idea. Actuallymy favorite broken tool here is xpermon++. Just got to see these strip charts... :-) Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message