<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 09/29/2012 01:39 AM, Charles Lepple wrote:
<blockquote
cite="mid:FDEEB286-E301-47CC-B42E-A8F7823B2471@gmail.com"
type="cite">
<pre wrap="">On Sep 28, 2012, at 11:43 AM, Manuel Wolfshant wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 09/28/2012 06:27 PM, <a class="moz-txt-link-abbreviated" href="mailto:twhitney@clearbearing.com">twhitney@clearbearing.com</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">quick question, Is there an issue with centos 5 that prevents it from running Nut greater then 2.2.3 ?
</pre>
</blockquote>
<pre wrap=""> No. It's just that there are no official packages. I have tried just yesterday to compile 2.6.6 and failed due to incompatible autoconf versions ( 2.59 in centos 5 vs 2.63 in C6), so a a bit more work will be needed.
</pre>
</blockquote>
<pre wrap="">
Theoretically, running autoconf shouldn't be necessary if you are compiling a NUT released tarball. Or am I misunderstanding your comment?
</pre>
</blockquote>
The package from Fedora's EPEL 6 has this in the build section:<br>
<br>
autoreconf -i<br>
%configure \<br>
[...]<br>
<br>
In the build system for RHEL6 this works fine. However , in the
environment created for RHEL5, it barfs:<br>
<br>
Sep 27 00:11:51 <wolfy> configure.in:100: error: possibly
undefined macro: AC_C_FLEXIBLE_ARRAY_MEMBER<br>
Sep 27 00:11:51 <wolfy> If this token and others are
legitimate, please use m4_pattern_allow.<br>
Sep 27 00:11:51 <wolfy> See the Autoconf documentation.<br>
Sep 27 00:11:51 <wolfy> configure.in:101: error: possibly
undefined macro: AC_C_VARARRAYS<br>
Sep 27 00:11:51 <wolfy> configure.in:111: error: possibly
undefined macro: AC_TYPE_LONG_DOUBLE<br>
Sep 27 00:11:51 <wolfy> configure.in:112: error: possibly
undefined macro: AC_TYPE_LONG_LONG_INT<br>
Sep 27 00:11:51 <wolfy> autoreconf: /usr/bin/autoconf failed
with exit status: 1<br>
<br>
My knowledge about using autoconf fluctuates between nil and close
to zero so I just tried tossing in a call to aclocal before using
autoreconf, but it failed as well:<br>
<blockquote>+ aclocal<br>
configure.in:683: warning: AC_LIBTOOL_SETUP was called before
AC_DISABLE_STATIC<br>
/usr/share/aclocal/libtool.m4:1997: AC_DISABLE_STATIC is expanded
from...<br>
configure.in:683: the top level<br>
+ autoreconf -i<br>
You should update your `aclocal.m4' by running aclocal.<br>
libtoolize: `config.guess' exists: use `--force' to overwrite<br>
libtoolize: `config.sub' exists: use `--force' to overwrite<br>
libtoolize: `ltmain.sh' exists: use `--force' to overwrite<br>
configure.in:100: error: possibly undefined macro:
AC_C_FLEXIBLE_ARRAY_MEMBER<br>
If this token and others are legitimate, please use
m4_pattern_allow.<br>
See the Autoconf documentation.<br>
configure.in:101: error: possibly undefined macro: AC_C_VARARRAYS<br>
configure.in:111: error: possibly undefined macro:
AC_TYPE_LONG_DOUBLE<br>
configure.in:112: error: possibly undefined macro:
AC_TYPE_LONG_LONG_INT<br>
autoreconf: /usr/bin/autoconf failed with exit status: 1<br>
</blockquote>
<br>
<br>
At which point I went back to regular $DAYJOB and postponed reading
the autoconf docs till I'd have more time or a kind soul provided
the correct recipe, whichever comes first.<br>
<br>
<br>
</body>
</html>