Re: pkg/46710: pkgsrc-2012Q2 xosview won't build on amd64/6.0

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

The following reply was made to PR pkg/46710; it has been noted by GNATS.

From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/46710: pkgsrc-2012Q2 xosview won't build on amd64/6.0
Date: Tue, 17 Jul 2012 03:40:22 -0400

 On Mon, 16 Jul 2012 19:15:00 +0000 (UTC)
 Ephaeton%gmx.net@localhost wrote:
 
 > c++ -O2 -pipe -DUVM -I/usr/pkg/include -O2 -pipe -DUVM -I/usr/pkg/include  
 > -I/usr/pkg/include  -DXOSVIEW_VERSION=\"1.8.3\" 
 > -I/space/obj/sysutils/xosview/work/xosview-1.8.3 
 > -I/space/obj/sysutils/xosview/work/xosview-1.8.3/bsd -DPACKAGE_NAME=\"\" 
 > -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
 > -DPACKAGE_BUGREPORT=\"\" -DHAVE_BOOL=1 -DLONG_LONG=long\ long 
 > -DHAVE_SNPRINTF=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
 > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_IOSTREAM=1 
 > -DHAVE_FSTREAM=1 -DHAVE_XPM=1 -DXOSVIEW_NETBSD=1 -DHAVE_SWAPCTL=1 
 > -DHAVE_BATTERY_METER=1 -DHAVE_USLEEP=1 -I..  -c btrymeter.cc -o btrymeter.o
 > btrymeter.cc:23:28: fatal error: machine/apmvar.h: No such file or directory
 > compilation terminated.
 > *** Error code 1
 >      
 > >How-To-Repeat:
 > on 6.0/amd64, go to $PKGSRC, cvs update to -rpkgsrc-2012Q2,
 > cd sysutils/xosview && make
 
 Unfortunately, I'm unable to reproduce this error on netbsd-6/amd64.
 I can't find any attempt to build btrymeter.cc in the backlog either,
 however, so I assume that this only matters if a battery meter was
 found at configure time, setting -DHAVE_BATTERY_METER.  This is itself
 bogus, as one may want to select which features to support when
 building, to run the package on another system...
 
 Meanwhile, does gkrellm work better for you?  Ideally our native systat
 should also be more powerful, but that's another matter :)
 
 I'll try to look further into this when I have more time and possibly
 replace those detected options by mk options, or simply force all
 options to be enabled; then it should be easier to reproduce the build
 error and patch the package.  It also seems that neither netbsd-5 nor
 netbsd-6 have machine/apmvar.h exposed in a machine-independent way
 anymore (and we have envsys for sensors today):
 
 cd /usr/include/ && grep -r apmvar *
 i386/apmvar.h:/*        $NetBSD: apmvar.h,v 1.25 2008/04/28 20:23:24 martin 
Exp $       */
 -- 
 Matt