similar to: configure.ac:9: error: possibly undefined macro: AC_CONFIG_MACRO_DIRS

Displaying 20 results from an estimated 9000 matches similar to: "configure.ac:9: error: possibly undefined macro: AC_CONFIG_MACRO_DIRS"

2015 Jul 15
0
configure.ac:9: error: possibly undefined macro: AC_CONFIG_MACRO_DIRS
On Wed, Jul 15, 2015 at 02:35:33PM +0200, Florent B wrote: > I have found the problem, replacing > > AC_CONFIG_MACRO_DIRS([m4]) > > with > > AC_CONFIG_MACRO_DIR([m4]) > > in configure.ac seems to solve the problem. > > It is about automake version, I have 1.11.6 (wheezy) and it needs 1.14 > to use DIRS. > > How to make it work for every version ?
2015 Jul 15
1
configure.ac:9: error: possibly undefined macro: AC_CONFIG_MACRO_DIRS
On Wed, Jul 15, 2015 at 02:42:13PM +0200, Florent B wrote: > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --without-zlib --with-lzo --with-openssl > > is then failing on > > ./configure: line 5083: syntax error near unexpected token > `-DFORTIFY_SOURCE=2,' > ./configure: line 5083: ` AX_CHECK_COMPILE_FLAG(-DFORTIFY_SOURCE=2, >
2015 Jul 15
0
configure.ac:9: error: possibly undefined macro: AC_CONFIG_MACRO_DIRS
15.07.2015 16:23, Michael Tokarev ?????: > 15.07.2015 16:20, Guus Sliepen ?????: > >>> ./configure: line 5083: ` AX_CHECK_COMPILE_FLAG(-DFORTIFY_SOURCE=2, > > Should it be AC_CHECK_COMPILE_FLAG not AX_... ? ..nope it shouldn't. ;) /mjt
2018 Jul 28
2
Error building nbdkit on RHEL 7.5 - possibly undefined macro: PKG_CHECK_VAR
I'm trying to build upstream source on RHEL 7.5 and get this error: # autoreconf -i libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying
2018 Jul 28
0
Re: Error building nbdkit on RHEL 7.5 - possibly undefined macro: PKG_CHECK_VAR
On Sat, Jul 28, 2018 at 09:26:06PM +0300, Nir Soffer wrote: > I'm trying to build upstream source on RHEL 7.5 and get this error: > > # autoreconf -i > libtoolize: putting auxiliary files in `.'. > libtoolize: copying file `./ltmain.sh' > libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. > libtoolize: copying file `m4/libtool.m4' > libtoolize:
2008 Dec 29
1
AC_CONFIG_MACRO_DIR
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
2015 Jul 27
0
./configure: line 5083: syntax error near unexpected token `-DFORTIFY_SOURCE=2, '
Hi all, I always have a problem to compile Tinc 1.1 on Debian Wheezy (after AC_CONFIG_MACRO_DIRS problem was solved). Now I get : ./configure: line 5083: syntax error near unexpected token `-DFORTIFY_SOURCE=2,' ./configure: line 5083: ` AX_CHECK_COMPILE_FLAG(-DFORTIFY_SOURCE=2, CPPFLAGS="$CPPFLAGS -DFORTIFY_SOURCE=2")' Just to be clear, I run : rm -Rf /usr/src/tinc git
2017 Aug 01
0
configure.ac
If you check developer.r-project.org, you'll find links to the scripts that we use for building releases and pre-releases of R. These are usually run on a Mac, but shouldn't require much change for Linux. In particular, notice this lead-in in the prerelease script: rm -rf BUILD-dist mkdir BUILD-dist cd R aclocal -I m4 autoconf cd ../BUILD-dist ....etc.... -pd > On 1 Aug 2017, at
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
2017 Jan 26
0
Undefined behavior of head() and tail() with n = 0
>>>>> Florent Angly <florent.angly at gmail.com> >>>>> on Wed, 25 Jan 2017 16:31:45 +0100 writes: > Hi all, > The documentation for head() and tail() describes the behavior of > these generic functions when n is strictly positive (n > 0) and > strictly negative (n < 0). How these functions work when given a zero >
2008 Jul 30
4
panic action on samba 3.2
Hi, during I make a some du command (du -sh), samba has been disturb and sent a panic action : Last line of smbd.log : [2008/07/30 15:36:09, 0] lib/util_str.c:safe_strcpy_fn(709) ERROR: string overflow by 1 (16 - 15) in safe_strcpy [10.217.7.3/255.255.252.0] [2008/07/30 16:04:43, 0] lib/util_str.c:safe_strcpy_fn(709) ERROR: string overflow by 1 (16 - 15) in safe_strcpy
2013 May 08
1
[PATCH] opusfile configury fixes.
[this time compeled the mail]. The autogen.sh of opusfile doesn't work for me: Updating build configuration files for opusfile, please wait.... configure.ac:8: installing `./install-sh' configure.ac:8: installing `./missing' Makefile.am:10: Libtool library used but `LIBTOOL' is undefined Makefile.am:10: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
2017 Jan 27
0
Undefined behavior of head() and tail() with n = 0
Martin, I agree with you that +0 and -0 should generally be treated as equal, and R does a fine job in this respect. The Wikipedia article on signed zero (https://en.wikipedia.org/wiki/Signed_zero) echoes this view but also highlights that +0 and -0 can be treated differently in particular situations, including their interpretation as mathematical limits (as in the 1/-0 case). Indeed, the main
2017 Jan 26
2
Undefined behavior of head() and tail() with n = 0
In addition, signed zeroes only exist for floating point numbers - the bit patterns for as.integer(0) and as.integer(-0) are identical. Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, Jan 26, 2017 at 1:53 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Florent Angly <florent.angly at gmail.com> >>>>>> on Wed, 25 Jan 2017
2018 Aug 14
5
[PATCH 1/4] build: Use LT_INIT in configure.ac.
Avoids the warning: libtoolize: Remember to add 'LT_INIT' to configure.ac. This is the new name for AC_PROG_LIBTOOL, so I removed that. However to use this macro we must enable AC_USE_SYSTEM_EXTENSIONS. (AC_GNU_SOURCE was removed back in 2011). --- configure.ac | 5 +++++ m4/guestfs-progs.m4 | 1 - 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/configure.ac
2013 Mar 12
2
I reinstalled OS X, now FLAC 1.3 git won't compile.
Are there any dependencies that I need, but don't have? I've got doxygen, libogg, automake, autoconf, libtool, valgrind, docbook, nasm, yasm, libiconv. the Autogen.sh script fails with: "Updating build configuration files for FLAC, please wait.... configure.ac:308: warning: macro 'AM_ICONV' not found in library configure.ac:309: warning: macro 'AM_LANGINFO_CODESET'
2013 Oct 26
2
[PATCH] 1. changes for vdiskadm on illumos based platform
2. update ZFS in libfsimage from illumos for pygrub diff -r 7c12aaa128e3 -r c2e11847cac0 tools/libfsimage/Rules.mk --- a/tools/libfsimage/Rules.mk Thu Oct 24 22:46:20 2013 +0100 +++ b/tools/libfsimage/Rules.mk Sat Oct 26 20:03:06 2013 +0400 @@ -2,11 +2,19 @@ include $(XEN_ROOT)/tools/Rules.mk CFLAGS += -Wno-unknown-pragmas -I$(XEN_ROOT)/tools/libfsimage/common/
2013 Jan 17
1
flac fails to build shared library under MinGW
On Thu, Jan 17, 2013 at 8:04 AM, Erik de Castro Lopo <mle+la at mega-nerd.com>wrote: > I suggest that you compile FLAC out of the git repository > which is here: > > https://git.xiph.org/?p=flac.git;a=summary > > We're currently working up to a release. > > Thanks for your fast reply and the tip, but I can't generate configure with git version: $
2009 May 24
1
Problems with ioloop on MacOS
I've been using the macports version of dovecot, which is 1.1.11, on MacOS 10.5.6 $ /opt/local/sbin/dovecot --exec-mail imap Fatal: kevent(EV_ADD, 0) failed: Operation not supported This version is configured --with-ioloop=kqueue The problem seems to be known, if not understood: http://lists.apple.com/archives/Darwin-userlevel/2008/Dec/msg00010.html However, if I use
2017 Jan 25
3
Undefined behavior of head() and tail() with n = 0
Hi all, The documentation for head() and tail() describes the behavior of these generic functions when n is strictly positive (n > 0) and strictly negative (n < 0). How these functions work when given a zero value is not defined. Both GNU command-line utilities head and tail behave differently with +0 and -0: http://man7.org/linux/man-pages/man1/head.1.html