Hi,

I am using SUSE Linux 12. I am trying to install unixODBC 2.3.7 but the installation is stopping in between. I am executing command ./configure and the execution is showing below steps and stopping after the last line:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gawk... (cached) gawk
checking for bison... no
checking for byacc... no
checking for style of include used by make... GNU
checking for gcc... gcc


I am not sure whether I am missing something or what.. Please assist..

Thanks,
Niranjan

usually it prints some hints too. But probably you need to install bison first.

1 members found this post helpful.

Sorry, but you didn't post accurately. It did *NOT* just stop after the gcc line...it would have, as pan64 said, given you SOME sort of error/message/hint, which you didn't post. But a couple of better questions come to mind:

• Why aren't you installing this from packages? unixODBC is available through the software repositories. If you're using openSUSE 12..that is *VERY* old, and you really need to upgrade. If you're using SLES 12, then contact SuSE support and they can tell you how to install it.
• What are you trying to accomplish? Because (programmatically), you can access pretty much any DB over the network, without an ODBC driver.

I tried installing bison but while running configure command it again stuck after the same line (checking for gcc... gcc).

It is getting stuck after some time. We are using SLES 12.2.
I am trying to accomplish HANA Smart Data Integration and for that I wanted to check connectivity for SQL Server. That is why I am trying to install unixODBC and then make DSN entry in .odbc.ini file.

The last time I executed command configure, it gave error as -> ./configure: fork: Cannot allocate memory
We have 24 GB RAM allocated for the HANA Express Edition VM. When I checked memory utilization, RAM is completely getting utilized and that is why the configuration is getting stuck.

it is very unlikely (I mean to eat up 24GB of RAM). You need to find a log file which will tell you how the check itself is constructed/running. Also usually configure has some flags, you may try to check them.

Are there any specific logs which I need to check.
After execution, I checked configure.log file and its last lines are as of below:


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1995: checking for a BSD-compatible install
configure:2051: result: /usr/bin/install -c
configure:2062: checking whether build environment is sane
configure:2105: result: yes
configure:2133: checking for a thread-safe mkdir -p
configure:2172: result: /usr/bin/mkdir -p
configure:2185: checking for gawk
configure:2201: found /usr/bin/gawk
configure:2212: result: gawk
configure:2223: checking whether make sets $(MAKE)
configure:2244: result: yes
configure:2447: checking build system type
configure:2465: result: x86_64-unknown-linux-gnu
configure:2487: checking host system type
configure:2502: result: x86_64-unknown-linux-gnu
configure:2572: checking for gcc
configure:2588: found /usr/share/bash-completion/completions/gcc
configure:2599: result: gcc
configure:2837: checking for C compiler version
configure:2844: gcc --version >&5