From: Simon H. <si...@it...> - 2013-07-18 13:50:42
|
Hello, I am trying to compile ipsec-tools on centos 64bit 6.4, with ldap support. I have installed the dev tools: yum groupinstall "Development Tools" I have the following centos packages installed: libpam openssl openssl-devel openldap-devel kernel-devel kernel-header I am using the source code from the ipsec tools sourceforge website. My configure command is: ./configure --enable-stats --enable-hybrid --enable-shared --enable-frag --enable-adminport --enable-rc5 --enable-idea --enable-dpd --prefix=/usr --enable-security-context=yes --with-kernel-headers=/usr/include --with-flexlib=-lfl --with-libldap --with-libpam When I run configure, it fails with the following: checking getaddrinfo bug... buggy configure: error: Broken getaddrinfo() is no longer supported. Aborting. The exact same configure command works on ubuntu 12.04 (but I disable security context support). What am I doing wrong? I have tried ipsec-tools 0.80 and 0.81, same result. Many thanks, Simon Harding |
From: Mick <mic...@gm...> - 2013-07-18 15:08:49
Attachments:
signature.asc
|
On Thursday 18 Jul 2013 14:35:18 Simon Harding wrote: > My configure command is: > ./configure --enable-stats --enable-hybrid --enable-shared --enable-frag > --enable-adminport --enable-rc5 --enable-idea --enable-dpd --prefix=/usr > --enable-security-context=yes --with-kernel-headers=/usr/include > --with-flexlib=-lfl --with-libldap --with-libpam > > When I run configure, it fails with the following: > checking getaddrinfo bug... buggy > configure: error: Broken getaddrinfo() is no longer supported. Aborting. Did you look in your config.log just before this error comes up for something more obvious that causes this failure? > The exact same configure command works on ubuntu 12.04 (but I disable > security context support). Are the /etc/hosts files the same in both machines? > What am I doing wrong? I have tried ipsec-tools 0.80 and 0.81, same result. Last time I used CentOS was 4-5 years ago, so I'm not the best person to advise. I would start with the config.log as mentioned above to see what causes this error. HTH. -- Regards, Mick |