On Sat, Apr 19, 2008 at 6:52 AM, Roger Price <[EMAIL PROTECTED]> wrote: > On Sat, 19 Apr 2008, Arjen de Korte wrote: > > > > You're making this far more complex than needed. With the RPMs I sent > you, > > > I also included the source RPM for nut (which was built on openSUSE 10.3 > > > by the way). Extract that with > > > rpm -Uvh nut-2.2.2-pre2.src.rpm > > > and then rebuild the lot with > > > rpmbuild -ba /usr/src/packages/SPECS/nut.spec > > > There is also a command to do this in one go, but I don't remember this > at > > > the moment. > > I just found it > > rpmbuild --rebuild nut-2.2.2-pre2.src.rpm > > should do the trick. > > Lets go! The command > > rpmbuild --rebuild nut-2.2.2-pre2.src.rpm > gives me > > Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.67245 > + umask 022 > + cd /usr/src/packages/BUILD > + cd /usr/src/packages/BUILD > + rm -rf nut-2.2.2 > + tar -xf /usr/src/packages/SOURCES/nut-2.2.2-pre2.tar > + cd nut-2.2.2 > ++ /usr/bin/id -u > + '[' 0 = 0 ']' > + /bin/chown -Rhf root . > ++ /usr/bin/id -u > + '[' 0 = 0 ']' > + /bin/chgrp -Rhf root . > + /bin/chmod -Rf a+rX,u+w,g-w,o-w . > + autoreconf -f -i > configure.in:69: error: possibly undefined macro: AC_PROG_LIBTOOL
Roger, Do you have libtool installed? Arjen, The tarballs should have the configure script already generated - why is autoreconf being called? -- - Charles Lepple _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
