configure scripts ends with status 2 on CentOS 6.3
GoogleCodeExporter opened this issue · 2 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. ./configure gives error
What is the expected output? What do you see instead?
Expect the configure script to finish, instead an error is thrown.
checking for bash... /bin/sh
./configure: line 3682: syntax error near unexpected token `fi'
./configure: line 3682: `fi'
What version of the product are you using? On what operating system?
1.0.10, CentOS 6.3.
Please provide any additional information below.
# ./configure ; echo $?
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for bash... /bin/sh
./configure: line 3682: syntax error near unexpected token `fi'
./configure: line 3682: `fi'
2
# echo $SHELL
/bin/bash
# cat /etc/redhat-release
CentOS release 6.3 (Final)
]# bash --version
GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
Original issue reported on code.google.com by mattias....@mobenga.com on 14 Mar 2013 at 11:47
GoogleCodeExporter commented
It works after downloading the package again. I should have checked that prior
to posting, sorry.
Original comment by mattias....@mobenga.com on 14 Mar 2013 at 11:49
GoogleCodeExporter commented
No problem. Glad you got it fixed.
Original comment by archie.c...@gmail.com on 14 Mar 2013 at 4:50
- Changed state: Invalid