similar to: NUT and Automake

Displaying 20 results from an estimated 8000 matches similar to: "NUT and Automake"

2006 Oct 16
1
doxygen (was: Re: NUT and Automake)
On 10/15/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > I have converted NUT's build system to Automake/Libtool. Right now, > the new build system is contained in the "automake" branch, at: Wow... this is really nice. Thanks for taking the time to do the conversion. > drivers/Doxyfile - this seems to belong to Charles. Perhaps >
2007 May 22
5
release?
Hi developers, I would like to propose making a release soon from the current NUT trunk. There have been a lot of important changes since 2.0.5: new drivers added/refined (e.g. megatec_usb); the switch to Automake; the renaming of newhidups to usbhid-ups; automatic installation of hotplugging files; IPv6 support; improvements to the tripplite_usb driver; improvements to the gamatronic driver;
2019 Jan 13
3
[FTS Xapian] Beta release
You copied your Makefile.am?there. Stephan made you a working version, can you try that? (sorry for dup) Aki -------- Original message --------From: Joan Moreau <jom at grosjo.net> Date: 13/01/2019 21:39 (GMT+02:00) To: Stephan Bosch <stephan at rename-it.nl> Cc: Aki Tuomi <aki.tuomi at open-xchange.com> Subject: Re: [FTS Xapian] Beta release I used the skeleton from Aki :
2019 Jan 13
3
[FTS Xapian] Beta release
Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot: > > I tried to combined it, the "autoreconf" errors are solved > > Now, when I type "make install", the lib is not pushed into dovecot > folder, but somewhere in /usr/local/... > > How to adjust this to have it arriving in the proper folder ? > Depends on your system. It mostly a matter of setting
2006 Oct 03
1
NUT release process (was: Stack corruption in newhidups.c)
2006/10/2, Peter Selinger <selinger@mathstat.dal.ca>: > Arnaud Quette wrote: > > > > 2006/9/29, Peter Selinger <selinger@mathstat.dal.ca>: > > > > > I don't really understand the purpose of the "Testing" branch. It has > > > not been touched since July, as far as I can see. I also don't > > > understand NUT's release
2019 Jan 14
2
[FTS Xapian] Beta release
In your README.md, perhaps "This project intends to provide a straightforward and simple *procedure *to configure FTS plugin for Dovecot, leveraging the efforts by the Xapian.org team." is better?? Also in the part after cloning from git: ./configure --prefix=/usr --with-dovecot=/path/to/dovecot [ This /path/to/dovecot is not obvious. Is it the dovecot binary or what??] On Mon, 14 Jan
2007 Mar 06
3
make errors on solaris express dev 02/07
make fails at drivers: make[1]: Entering directory `/export/home/zoly/Documents/trunk/drivers' /bin/sh ../libtool --tag=CC --mode=link gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/sfw/include -g -Dsolaris2 -I. -I/usr/sfw/include -O -Wall -Wsign-compare -o al175 al175.o ../common/libcommon.a ../common/upsconf.o
2019 Jan 14
3
[FTS Xapian] Beta release
Testing a compile on FreeBSD. gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src' /bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo fts-backend-xapian.cpp libtool:
2007 Sep 08
4
bye!
Dear fellow NUT developers, after almost exactly two years as a NUT developer, I have concluded that this would be a good time to retire from active development. The project is in good shape, and the driver I was most involved with (usbhid-ups) is in better condition than ever, due to the excellent recent work of Arjen de Korte. Having already scaled back my activity for the last 6 months, I
2019 Jan 14
3
[FTS Xapian] Beta release
Hi, I installed and tested your version, but the indexer process crashes reproducible with the following command after about 2000 messages were indexed: doveadm index -u paul at iwascoding.com -q \* Jan 14 09:26:15 mail dovecot: indexer-worker(paul at iwascoding.com)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Mailbox sent: UID 2038: Opened mail because: fts indexing Jan 14 09:26:15 mail
2012 Jan 06
1
v2.1.rc3 released
http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz.sig Whops, rc2 was missing a file. I always run "make distcheck", which should catch these, but recently it has always failed due to clang static checking giving one "error" that I didn't really want to fix. Because of that the distcheck didn't finish and
2012 Jan 06
1
v2.1.rc3 released
http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz.sig Whops, rc2 was missing a file. I always run "make distcheck", which should catch these, but recently it has always failed due to clang static checking giving one "error" that I didn't really want to fix. Because of that the distcheck didn't finish and
2017 Aug 01
3
configure.ac
Hi, Just a quick mail to mention that I cannot generate a new configure script using autoconf or autoreconf. I had edited the configure.ac and thought ... "oh, that's my fault", but then I tried it on R-patched and R-3.4.1 without touching configure.ac and had the same problems. The "building R packages" documentation seems to suggest that "autoconf" should take
2019 Jan 14
2
[FTS Xapian] Beta release
Op 14-1-2019 om 13:40 schreef Aki Tuomi: > > Just to remind that now that there is a github repo for fts-xapian, > you could maybe open these issues there instead? > Although README.md currently says: "Please feel free to send your questions, together with the dovecot log file, to jom at grosjo.net <mailto:jom at grosjo.net> or to the dovecot ML dovecot at dovecot.org
2007 Apr 09
3
Red Hat Enterprise 3 build
I am working on getting the CentOS 3/Red Hat Enterprise 3 buildbot going, but I have hit a problem with the latest SVN build. Running './configure' works without any errors, (but I do note that it takes a long time on the drivers directory Makefile). Here is a copy of the configuration summary: Configuration summary: enable SSL development code: yes enable IPv6 support: yes build CGI
2007 Jan 03
2
building trunk
I've been wanting to build the trunk since Arjen added the powerpanel driver... been having a little trouble... after running these commands: /usr/local/libexec/automake19/aclocal -I m4 /usr/local/libexec/autoconf259/autoheader /usr/local/libexec/automake19/automake -ac /usr/local/libexec/autoconf259/autoconf ./configure --with-cgi --with-user=nutmon
2014 Sep 08
0
how to install NUT on raspberry pi
On Sep 8, 2014, at 9:03 AM, Roger Price <roger at rogerprice.org> wrote: > Charles: Since there is currently no user writeup for openSUSE in your list, maybe it would be useful to add this reference. Roger, thanks for the reminder - I thought we had added that link a while ago. It's committed to Git now, but we need to untangle a few things before it will show up on the web server.
2015 May 13
3
tinc 1.1 git: new automake needed?
Hallo, trying to compile the current 1.1 git snapshot under Debian Wheezy gives me: configure.ac:7: option `info-in-builddir' not recognized autoreconf: automake failed with exit status: 1 Do I now need a specific newer version of automake? Seems to be the result of commit 13f9bc1ff199bea46 "Add support for out-of-tree ("VPATH") builds." Undoing the change to
2006 Dec 04
1
Re: [nut-commits] svn commit r609 - trunk
Charles Lepple wrote: > > Author: clepple-guest > Date: Mon Dec 4 03:00:57 2006 > New Revision: 609 > > Modified: > trunk/ChangeLog > trunk/configure.in > Log: > Undoing changeset [608]. It fails with this error: > > configure: error: conditional "HAVE_LIBUSB" was never defined. > Usually this means the macro was only invoked
2014 Sep 08
2
how to install NUT on raspberry pi
On Mon, 8 Sep 2014, Charles Lepple wrote: > On Sep 8, 2014, at 2:26 AM, Flavio.Boschiggia at infineon.com wrote: >> I would like connect it by usb on my server raspberry pi. >> Someone knows a simple tutorial to send me? I did some test without success..... > > We try to collect tutorial links here: > http://www.networkupstools.org/documentation.html#_offsite_links In