similar to: autoconf version requirements?

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Sun Nov 16 13:00:30 2008 > New Revision: 1560 > > Log: > Generated by libtool and should not be versioned. > > Modified: > trunk/ (props changed) Right, that didn't work out quite the way I intended. Can someone please set the svn:ignore property on

Charles, When running autoreconf in the trunk, I get a couple of additional files since I upgraded to openSUSE 11.1. Most likely, this is due to a newer version of the auto(whatever) tools that are used. Or I never looked at this more closely before. libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file

On Dec 31, 2009, at 8:45 AM, Arjen de Korte wrote: > Author: adkorte-guest > Date: Thu Dec 31 13:45:16 2009 > New Revision: 2218 > > Log: > Add pkg-config as method to retrieve CFLAGS and LDFLAGS (but fall > back to libusb-config) > > Modified: > trunk/m4/nut_check_libusb.m4 Arjen, I'm not sure you want parentheses in the shell script fragments. Search for

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

While the changes to m4/nut_check_libssl.m4 have improved detection of OpenSSL on Solaris, it breaks on platforms that did not have pkg-config from the vendor. -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: aquette > Date: Sat Nov 15 22:47:26 2008 > New Revision: 1557 > > Log: > GNU libtool update > > Modified: > trunk/ChangeLog > trunk/configure.in > trunk/ltmain.sh I think 'ltmain.sh' is a generated file (at least, I hope it is), this change severely broke compilation here. I had to

Citeren clepple+buildbot op ghz.cc: > The Buildbot has detected a new failure of FreeBSD-i686. > Full details are available at: > http://buildbot.ghz.cc/public/nut/FreeBSD-i686/builds/35 Charles, It seems that m4/nut_check_libhal.m4 fails to detect the proper path where to install the .fdi files. I have no idea where these files live on FreeBSD, so could you please find out what

2010/11/4 Arjen de Korte > Author: adkorte-guest > Date: Thu Nov 4 22:40:51 2010 > New Revision: 2671 > URL: http://trac.networkupstools.org/projects/nut/changeset/2671 > > Log: > Exclude -I. and extra developer warning flags with Net-SNMP support enabled > (using them is the responsibility of the NUT developers) > > Modified: >

Citeren Frederic BOHE <fbohe-guest op alioth.debian.org>: > Author: fbohe-guest > Date: Fri Nov 26 14:01:35 2010 > New Revision: 2705 > URL: http://trac.networkupstools.org/projects/nut/changeset/2705 > > Log: > Add regex library for drivers (by Arnaud Quette) > > Modified: > branches/windows_port/drivers/Makefile.am Why is this needed? The value of

Series of cleanups to autotools build config files to utilize the available xorg-server macros, defaults and more closely match other modern Xorg drivers. Notable improvements: - gitignore fully covers potential build artifacts - Simplify logic given stated minimum required version of xorg-server 1.8 - Remove use of deprecated, outdated or no longer required macros - Utilize xorg macros where

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Log: > Use the 'nss_compat_ossl' compatibility layer to use the Mozilla NSS > library instead of OpenSSL (we might want to include native support > in the future, but this will at least allow a quick migration for > testing purposes) I don't recall that we ever discussed the possibility of

Hi. I want to add some code to flac and am having trouble building it out of cvs. I've had several problems, most of which were pretty easy to work around or had already been discussed here. But this one has me stumped (though I am admittedly new to autoconf, automake, and libtool). Here's the problem. autoconf does not see any definition for AC_PROG_LIBTOOL. There is such a

Hello, I can compile metadata plugin using debian squeeze + wheezy. But build on suse enterprise server 9,10 and 11 failed. The metadata plugin require autoconf-2.65 which i too new. On the other side I can build the dovecot-2.2.4 and pigeonhole-0.4.0 plugin without problems: dovecot require autoconf-2.59 and pigeonhole does not require any specific autoconf version. I asked the authors of the

On 2/23/07, Reid Spencer <rspencer at reidspencer.com> wrote: > > However, if I run the AutoRegen.sh script (after modifying it to > > accept autoconf 2.61, which I think is fine as gentoo slots it the > > same as the 2.5[0-9] versions), the configure no longer works: > > ~/programming/llvm-1.9/projects/zhe $ cd autoconf/ > >

This patch series modernizes various aspects of the autotools based build system. There is a lot more that could and should be done, but I tried to stay conservative for now and just resolve some of the most obvious issues. Max Horn (5): configure: replace XIPH_C_FIND_ENDIAN by AC_C_BIGENDIAN autogen.sh: replace this by a simple call to autoreconf configure: always print

I'm trying to follow docs/Projects.html to use llvm in a project of my own. If I just copy the sample directory, running configure in the new one works fine: ~/programming/llvm-1.9/projects $ cp -a sample/ zhe ~/programming/llvm-1.9/projects $ cd zhe/ ~/programming/llvm-1.9/projects/zhe $ ./configure configure: creating ./config.status config.status: creating Makefile.common config.status:

Hello Scott, On Wed, 2007-02-21 at 18:57 -0500, me22 wrote: > I'm trying to follow docs/Projects.html to use llvm in a project of my own. > > If I just copy the sample directory, running configure in the new one > works fine: > ~/programming/llvm-1.9/projects $ cp -a sample/ zhe > ~/programming/llvm-1.9/projects $ cd zhe/ > ~/programming/llvm-1.9/projects/zhe $

Charles, Do you know why Debian etch accepts the quadrigraph '@<:@' but not two consecutive ones? Even with a space in between it doesn't work, although a single instance is processed correctly. Best regards, Arjen -- Please keep list traffic on the list

I just upgraded the FreeBSD buildbot machine from 6.4 to 8.0, and I ran across some interesting differences. The libusb API that we use (0.1) is available in /usr/include/usb.h and /usr/lib/libusb.* as before, but it seems to be the compatibility layer from libusb 1.0. However, it doesn't include the libusb-config binary. This is from the 'ports' Makefile for NUT: ########## - -

Charles, I was looking into why CGI isn't build on the Ubuntu box. Although everything seems to be available, it is currently showing checking for gd version via gdlib-config... 2.0.35 checking for gd include flags... -I/usr/include checking for gd library flags... -L/usr/lib -Wl,-Bsymbolic-functions -ljpeg -lfreetype -lpng12 -lz -lm checking for gd.h... yes checking for gdfontmb.h...