On 06/18/2017 05:42 PM, Charles Lepple wrote:
On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant
<[email protected] <mailto:[email protected]>> wrote:
running autogen.sh was triggered automatically. but even if I do it
explicitly, I still get:
+ autoreconf -i
configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call
detected in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
/usr/share/aclocal/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is
expanded from...
/usr/share/aclocal/libtool.m4:4161: _LT_LINKER_SHLIBS is expanded
from...
/usr/share/aclocal/libtool.m4:5236: _LT_LANG_C_CONFIG is expanded
from...
/usr/share/aclocal/libtool.m4:138: _LT_SETUP is expanded from...
/usr/share/aclocal/libtool.m4:67: LT_INIT is expanded from...
/usr/share/aclocal/libtool.m4:102: AC_PROG_LIBTOOL is expanded from...
configure.ac:887: the top level
[.... looong part of output deleted...]
configure.ac:1526: required file `scripts/augeas/nutupsconf.aug.in'
not found
configure.ac:1526: required file `scripts/devd/nut-usb.conf.in' not found
configure.ac:1526: required file `scripts/udev/nut-usbups.rules.in'
not found
Makefile.am: installing `./INSTALL'
autoreconf: automake failed with exit status: 1
This sounds like an autotools incompatibility. Which versions of
autoconf, automake, libtool, etc. are you using?
As I am a packager for Fedora & EPEL I usually try to rely exclusively
on the tools of the distribution ( RHEL / CentOS 6 in this case).
Otherwise the packages would not be accepted as they could not be built
using the official builders which use exclusively packages available in
the distribution itself. In this particular case though I have updated
some tools to versions from RHEL7 or Fedora so I am using:
autoconf-2.69-23.el6.noarch ( instead of distro's 2.63 )
automake-1.11.1-4.el6.noarch
libtool-2.2.6-15.5.el6.x86_64
libtool-ltdl-devel-2.2.6-15.5.el6.x86_64
m4-1.4.16-10.el6.x86_64 ( instead of 1.4.13 )
In the mean time, Buildbot generates snapshots using "make dist" that
do not require auto*. Since there have not been any recent builds,
they aren't on the first page of the waterfall, but usually there is a
link to the snapshot off of the Debian jessie builder when the branch
is rebuilt.
Here is the generic URL:
http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/snapshot/libusb-1.0/nut-latest.tar.gz
<http://buildbot.networkupstools.org/%7Ebuildbot/docker-debian-jessie/snapshot/libusb-1.0/nut-latest.tar.gz>
Thank a lot !
Now, conclusions after attempting builds ( with no docs included since
attempting to enable them triggers the errors related to missing or too
old tools mentioned by me in an earlier message )
- building against libsub 1.0 triggers the following 2 errors :
nutdrv_qx-nutdrv_qx.o: In function `ippon_command':
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:679:
undefined reference to `libusb_strerror'
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:692:
undefined reference to `libusb_strerror'
nutdrv_qx-nutdrv_qx.o: In function `fabula_command':
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:907:
undefined reference to `libusb_strerror'
nutdrv_qx-nutdrv_qx.o: In function `krauler_command':
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:770:
undefined reference to `libusb_strerror'
nutdrv_qx-nutdrv_qx.o: In function `sgs_command':
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:542:
undefined reference to `libusb_strerror'
nutdrv_qx-nutdrv_qx.o:/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:568:
more undefined references to `libusb_strerror' follow
[...]
libusb1.o: In function `nut_libusb_strerror':
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:484:
undefined reference to `libusb_strerror'
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:469:
undefined reference to `libusb_strerror'
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:479:
undefined reference to `libusb_strerror'
libusb1.o: In function `nut_libusb_open':
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:181:
undefined reference to `libusb_strerror'
/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:282:
undefined reference to `libusb_strerror'
libusb1.o:/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:289:
more undefined references to `libusb_strerror' follow
- building against libusb 0.1 does not change in any way the situation,
I still get the same error related to lack of ability to claim the interface
If you need a specific version for the .spec file, that link currently
points to
http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/snapshot/libusb-1.0/rb1314c693bef0ce639991dcee6e5742f25e94a88-753/nut-v2.7.4-418-gb1314c62.7.4.1.tar.gz
<http://buildbot.networkupstools.org/%7Ebuildbot/docker-debian-jessie/snapshot/libusb-1.0/rb1314c693bef0ce639991dcee6e5742f25e94a88-753/nut-v2.7.4-418-gb1314c62.7.4.1.tar.gz> (not
a typo; the code that generates the version stuck in both 2.7.4 and
2.7.4.1)
Thanks a lot. This is not needed as I can adjust the spec accordingly.
After all I build rpms since 2007... :)
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
