On Jun 3, 2014, at 10:34 PM, Bruno Salvador wrote:
> Anybody knows what configure command settings FreeNAS use to compile NUT?
I haven't tried building FreeNAS myself, but it looks like they are using the
ports tree to do the build. So there is a bit of indirection. I don't know the
exact source of all of the ports variables, but it should be close to stock
FreeBSD.
On FreeBSD 10.0, /usr/ports/sysutils/nut/Makefile contains this:
CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \
--program-transform-name="" \
--localstatedir=${STATEDIR} \
--datadir=${PREFIX}/etc/nut \
--with-drvpath=${PREFIX}/libexec/nut \
--with-statepath=${STATEDIR} \
--with-altpidpath=${STATEDIR} \
--with-pidpath=${STATEDIR} \
--with-pkgconfig-dir=${PREFIX}/libdata/pkgconfig \
--with-user=${NUT_USER} \
--with-group=${NUT_GROUP} \
--with-dev
I think ${PREFIX} is /usr/local by default.
(FreeNAS also enables libneon, but that only affects the netxml-ups driver.)
Your post mentioned this command line:
./configure --with-user=root --with-group=nut --exec_prefix=/usr/local
prefix=/usr/local --sysconfdir=/etc/local/nut --sbindir=/usr/local/sbin
--bindir=/usr/local/bin --with-drvpath=/usr/local/libexec/nut
--with-statepath=/var/run --with-pidpath=/var/db/nut
I don't know if the difference in "--with-pidpath=" matters.
Does the FreeNAS project have a Continuous Integration system like Buildbot or
Jenkins which might have build logs? That should show the exact ./configure
command line.
> More info on my journey:
> http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/
Thanks for posting this - I hope you don't mind that I CC'd you on the other
thread on nut-upsuser@, since it sounds like a similar UPS.
--
Charles Lepple
clepple@gmail
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
