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 programs: no build upsclient library: no build serial drivers: yes build SNMP drivers: yes build USB drivers: yes enable HAL support: no When I do a make, everything seems to go fine until the drivers directory: make[1]: Entering directory `/home/buildbot/trunk/drivers' Makefile:1597: *** missing separator. Stop. make[1]: Leaving directory `/home/buildbot/trunk/drivers' make: *** [all-recursive] Error 1 Line 1597 is the last line in the Makefile for the drivers directory. Here is a list of the make versions for my machine: automake-1.6.3-5 automake15-1.5-7 automake14-1.4p6-6 autoconf-2.57-3 autoconf213-2.13-6 Kernel version: 2.4.21-47.0.1.ELsmp (yes it is a dual processor machine) Am I missing something that NUT needs to build? Ron -- Ronald Reed - RHCE, GCUX Manager of Computer Operations ARM SGP ACRF Site (580)388-4053 Ext. 114 rreed@ops.sgp.arm.gov
[buildbot@crypt trunk]$ automake --version automake (GNU automake) 1.6.3 Written by Tom Tromey <tromey@redhat.com>. Copyright 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I will look into getting a newer automake installed. 1.6.3 is the current one for CentOS 3. Ron On Mon, 2007-04-09 at 14:13, Charles Lepple wrote:> On 4/9/07, Ronald Reed <rreed@ops.sgp.arm.gov> wrote: > > When I do a make, everything seems to go fine until the drivers > > directory: > > > > make[1]: Entering directory `/home/buildbot/trunk/drivers' > > Makefile:1597: *** missing separator. Stop. > > make[1]: Leaving directory `/home/buildbot/trunk/drivers' > > make: *** [all-recursive] Error 1 > > > > > > Line 1597 is the last line in the Makefile for the drivers directory. > > If this is the same problem you mentioned last night, then I think > these lines might be the root cause of the "make" error: > > $ autoreconf --install > libtoolize: `config.guess' exists: use `--force' to overwrite > libtoolize: `config.sub' exists: use `--force' to overwrite > libtoolize: `ltmain.sh' exists: use `--force' to overwrite > configure.in:10: `automake requires `AM_CONFIG_HEADER', not > `AC_CONFIG_HEADER' > drivers/Makefile.am:35: driverexec_PROGRAMS was already defined in > condition SOME_DRIVERS_FALSE, which implies condition SOME_DRIVERS_FALSE > WITH_SERIAL_TRUE > > # construct the list of drivers to build > driverexec_PROGRAMS (User, where = drivers/Makefile.am:35) +> { > SOME_DRIVERS_TRUE => $(DRIVER_BUILD_LIST) > SOME_DRIVERS_FALSE => > } > > That last part repeats multiple times, once for each driver I believe. > and then I get hundreds of the following: > > Use of uninitialized value in list assignment at /usr/bin/automake line > 8448. > Use of uninitialized value in concatenation (.) or string at > /usr/bin/automake line 8449. > : warning: automake does not support driverexec_PROGRAMS being defined > conditionally > > > > Here is a list of the make versions for my machine: > > > > automake-1.6.3-5 > > automake15-1.5-7 > > automake14-1.4p6-6 > > autoconf-2.57-3 > > autoconf213-2.13-6 > > What happens if you type "automake --version"? > > You can probably get rid of automake15, automake14 and autoconf213. It > might be that automake-1.6 is not new enough. > > Peter, any ideas?-- Ronald Reed - RHCE, GCUX Manager of Computer Operations ARM SGP ACRF Site (580)388-4053 Ext. 114 rreed@ops.sgp.arm.gov
OK, I updated automake and autoconf:
[buildbot@crypt trunk]$ autoconf --version
autoconf (GNU Autoconf) 2.61
[buildbot@crypt trunk]$ automake --version
automake (GNU automake) 1.9.6
Now the error is:
[buildbot@crypt trunk]$ autoreconf && ./configure && make
distcheck-light
configure.in:67: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /usr/local/bin/autoconf failed with exit status: 1
So, do I have an older version of libtool also?
Ron
On Mon, 2007-04-09 at 14:13, Charles Lepple wrote:> On 4/9/07, Ronald Reed <rreed@ops.sgp.arm.gov> wrote:
> > When I do a make, everything seems to go fine until the drivers
> > directory:
> >
> > make[1]: Entering directory `/home/buildbot/trunk/drivers'
> > Makefile:1597: *** missing separator. Stop.
> > make[1]: Leaving directory `/home/buildbot/trunk/drivers'
> > make: *** [all-recursive] Error 1
> >
> >
> > Line 1597 is the last line in the Makefile for the drivers directory.
>
> If this is the same problem you mentioned last night, then I think
> these lines might be the root cause of the "make" error:
>
> $ autoreconf --install
> libtoolize: `config.guess' exists: use `--force' to overwrite
> libtoolize: `config.sub' exists: use `--force' to overwrite
> libtoolize: `ltmain.sh' exists: use `--force' to overwrite
> configure.in:10: `automake requires `AM_CONFIG_HEADER', not
> `AC_CONFIG_HEADER'
> drivers/Makefile.am:35: driverexec_PROGRAMS was already defined in
> condition SOME_DRIVERS_FALSE, which implies condition SOME_DRIVERS_FALSE
> WITH_SERIAL_TRUE
>
> # construct the list of drivers to build
> driverexec_PROGRAMS (User, where = drivers/Makefile.am:35) +> {
> SOME_DRIVERS_TRUE => $(DRIVER_BUILD_LIST)
> SOME_DRIVERS_FALSE =>
> }
>
> That last part repeats multiple times, once for each driver I believe.
> and then I get hundreds of the following:
>
> Use of uninitialized value in list assignment at /usr/bin/automake line
> 8448.
> Use of uninitialized value in concatenation (.) or string at
> /usr/bin/automake line 8449.
> : warning: automake does not support driverexec_PROGRAMS being defined
> conditionally
>
>
> > Here is a list of the make versions for my machine:
> >
> > automake-1.6.3-5
> > automake15-1.5-7
> > automake14-1.4p6-6
> > autoconf-2.57-3
> > autoconf213-2.13-6
>
> What happens if you type "automake --version"?
>
> You can probably get rid of automake15, automake14 and autoconf213. It
> might be that automake-1.6 is not new enough.
>
> Peter, any ideas?
--
Ronald Reed - RHCE, GCUX
Manager of Computer Operations
ARM SGP ACRF Site
(580)388-4053 Ext. 114
rreed@ops.sgp.arm.gov
On 4/9/07, Ronald Reed <rreed@ops.sgp.arm.gov> wrote:> When I do a make, everything seems to go fine until the drivers > directory: > > make[1]: Entering directory `/home/buildbot/trunk/drivers' > Makefile:1597: *** missing separator. Stop. > make[1]: Leaving directory `/home/buildbot/trunk/drivers' > make: *** [all-recursive] Error 1 > > > Line 1597 is the last line in the Makefile for the drivers directory.If this is the same problem you mentioned last night, then I think these lines might be the root cause of the "make" error: $ autoreconf --install libtoolize: `config.guess' exists: use `--force' to overwrite libtoolize: `config.sub' exists: use `--force' to overwrite libtoolize: `ltmain.sh' exists: use `--force' to overwrite configure.in:10: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' drivers/Makefile.am:35: driverexec_PROGRAMS was already defined in condition SOME_DRIVERS_FALSE, which implies condition SOME_DRIVERS_FALSE WITH_SERIAL_TRUE # construct the list of drivers to build driverexec_PROGRAMS (User, where = drivers/Makefile.am:35) + { SOME_DRIVERS_TRUE => $(DRIVER_BUILD_LIST) SOME_DRIVERS_FALSE => } That last part repeats multiple times, once for each driver I believe. and then I get hundreds of the following: Use of uninitialized value in list assignment at /usr/bin/automake line 8448. Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : warning: automake does not support driverexec_PROGRAMS being defined conditionally> Here is a list of the make versions for my machine: > > automake-1.6.3-5 > automake15-1.5-7 > automake14-1.4p6-6 > autoconf-2.57-3 > autoconf213-2.13-6What happens if you type "automake --version"? You can probably get rid of automake15, automake14 and autoconf213. It might be that automake-1.6 is not new enough. Peter, any ideas? -- - Charles Lepple