Charles,
It looks like the buildbot no longer builds (if it ever did, I don
remember) the HAL addons, even if the requirements are met:
configure:9680: checking for libhal version via pkg-config (0.5.8
minimum required)
configure:9690: result: 0.5.11 found
configure:9694: checking for libhal cflags via pkg-config
configure:9703: result: -DDBUS_API_SUBJECT_TO_CHANGE
-I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
configure:9707: checking for libhal ldflags via pkg-config
configure:9716: result: -L/lib -lhal -ldbus-glib-1 -ldbus-1
-lgobject-2.0 -lglib-2.0
configure:9720: checking for libhal user via pkg-config
configure:9729: result: haldaemon
configure:9738: checking for hal-0.5.11 device match key
configure:9747: result: info.subsystem
configure:9755: checking for libhal Callouts path
configure:9776: result: using default (${exec_prefix}/lib/hal)
configure:9785: checking for libhal Device Information path
configure:9795: result: ${prefix}/share/hal/fdi/information/20thirdparty
[...]
configure:27034: checking whether to enable HAL support
configure:27036: result: no
This is probably due to the fact that building HAL addons is not
enabled automatically, but needs to be enabled specifically
(configure.in):
NUT_ARG_WITH([hal], [build and install HAL support], [no])
As far as I know, we did this on purpose so that people who only want
to use the 'classic' NUT, don get stumped by the automatic
installation of the HAL addons.
However, for the buildbot it would be nice if it would try to build
the HAL addons if the requirements are met. Is it possible to add
--with-hal=auto to the configuration flags for the buildbot?
Best regards, Arjen
--
Please keep list traffic on the list
2008/10/20 Arjen de Korte <nut+devel at de-korte.org>:> Charles, > > It looks like the buildbot no longer builds (if it ever did, I don > remember) the HAL addons, even if the requirements are met: > > configure:9680: checking for libhal version via pkg-config (0.5.8 > minimum required) > configure:9690: result: 0.5.11 found > configure:9694: checking for libhal cflags via pkg-config > configure:9703: result: -DDBUS_API_SUBJECT_TO_CHANGE > -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > configure:9707: checking for libhal ldflags via pkg-config > configure:9716: result: -L/lib -lhal -ldbus-glib-1 -ldbus-1 > -lgobject-2.0 -lglib-2.0 > configure:9720: checking for libhal user via pkg-config > configure:9729: result: haldaemon > configure:9738: checking for hal-0.5.11 device match key > configure:9747: result: info.subsystem > configure:9755: checking for libhal Callouts path > configure:9776: result: using default (${exec_prefix}/lib/hal) > configure:9785: checking for libhal Device Information path > configure:9795: result: ${prefix}/share/hal/fdi/information/20thirdparty > > [...] > > configure:27034: checking whether to enable HAL support > configure:27036: result: no > > This is probably due to the fact that building HAL addons is not > enabled automatically, but needs to be enabled specifically > (configure.in): > > NUT_ARG_WITH([hal], [build and install HAL support], [no]) > > As far as I know, we did this on purpose so that people who only want > to use the 'classic' NUT, don get stumped by the automatic > installation of the HAL addons. > > However, for the buildbot it would be nice if it would try to build > the HAL addons if the requirements are met. Is it possible to add > --with-hal=auto to the configuration flags for the buildbot? >I thought buildbot was using distcheck... so --with-all which results in also building hal support code. Isn't it the case? Arnaud