All, is anyone else having problems with using building FR3.0 I get the following: [root@boppity-new freeradius-server]# ./configure --prefix=/usr --with-large-files --with-raddbdir=/etc/raddb --with-experimental-modules --enable-developer | grep WARN configure: WARNING: snmpget not found - Simultaneous-Use and checkrad.pl may not work configure: WARNING: snmpwalk not found - Simultaneous-Use and checkrad.pl may not work configure: WARNING: pcap library not found, silently disabling the RADIUS sniffer. configure: WARNING: silently not building rlm_counter. configure: WARNING: FAILURE: rlm_counter requires: libgdbm. configure: WARNING: FAILURE: rlm_dbm requires: (ndbm.h or gdbm/ndbm.h or gdbm-ndbm.h) (libndbm or libgdbm or libgdbm_compat). configure: WARNING: silently not building rlm_dbm. configure: WARNING: the TNCS library isn't found! configure: WARNING: silently not building rlm_eap_tnc. configure: WARNING: FAILURE: rlm_eap_tnc requires: -lTNCS. configure: WARNING: silently not building rlm_eap_pwd. configure: WARNING: FAILURE: rlm_eap_pwd requires: EC_GROUP_free. configure: WARNING: silently not building rlm_eap_ikev2. configure: WARNING: FAILURE: rlm_eap_ikev2 requires: libeap-ikev2 EAPIKEv2/connector.h. configure: WARNING: silently not building rlm_ippool. configure: WARNING: FAILURE: rlm_ippool requires: libgdbm. configure: WARNING: silently not building rlm_opendirectory. configure: WARNING: FAILURE: rlm_opendirectory requires: membership.h. configure: WARNING: silently not building rlm_pam. configure: WARNING: FAILURE: rlm_pam requires: libpam. configure: WARNING: silently not building rlm_python. configure: WARNING: FAILURE: rlm_python requires: Python.h libpython2.6. configure: WARNING: hiredis libraries not found. Use --with-redis-lib-dir=<path>. configure: WARNING: hiredis headers not found. Use --with-redis-include-dir=<path>. configure: WARNING: silently not building rlm_redis. configure: WARNING: FAILURE: rlm_redis requires: libhiredis hiredis.h. configure: WARNING: hiredis libraries not found. Use --with-redis-lib-dir=<path>. configure: WARNING: hiredis headers not found. Use --with-redis-include-dir=<path>. configure: WARNING: silently not building rlm_rediswho. configure: WARNING: FAILURE: rlm_rediswho requires: libhiredis hiredis.h. configure: WARNING: silently not building rlm_rest. configure: WARNING: FAILURE: rlm_rest requires: curl/curl.h. configure: WARNING: silently not building rlm_ruby. configure: WARNING: FAILURE: rlm_ruby requires: ruby-binary. configure: WARNING: silently not building rlm_sql_postgresql. configure: WARNING: FAILURE: rlm_sql_postgresql requires: libpq-fe.h libpq. configure: WARNING: silently not building rlm_sql_iodbc. configure: WARNING: FAILURE: rlm_sql_iodbc requires: libiodbc isql.h. configure: WARNING: Sqlite libraries not found. Use --with-sqlite-lib-dir=<path>. configure: WARNING: Sqlite headers not found. Use --with-sqlite-include-dir=<path>. configure: WARNING: silently not building rlm_sql_sqlite. configure: WARNING: FAILURE: rlm_sql_sqlite requires: libsqlite3 sqlite.h. configure: WARNING: silently not building rlm_sql_db2. configure: WARNING: FAILURE: rlm_sql_db2 requires: libdb2 sqlcli.h. configure: WARNING: oracle headers not found. Use --with-oracle-include-dir=<path>. configure: WARNING: silently not building rlm_sql_oracle. configure: WARNING: FAILURE: rlm_sql_oracle requires: oci.h. configure: WARNING: silently not building rlm_sql_unixodbc. configure: WARNING: FAILURE: rlm_sql_unixodbc requires: libodbc sql.h. configure: WARNING: silently not building rlm_sql_firebird. configure: WARNING: FAILURE: rlm_sql_firebird requires: libfbclient ibase.h. configure: WARNING: MySQL libraries not found. Use --with-mysql-lib-dir=<path>. configure: WARNING: MySQL headers not found. Use --with-mysql-include-dir=<path>. configure: WARNING: silently not building rlm_sql_mysql. configure: WARNING: FAILURE: rlm_sql_mysql requires: libmysqlclient_r mysql.h. [root@boppity-new freeradius-server]# make Making all in src... Making all in src/include... gmake[4]: Nothing to be done for `all'. Making all in src/lib... CC dict.c gmake[4]: /usr/local/src/freeradius-server/libtool: Command not found gmake[4]: *** [dict.lo] Error 127 gmake[3]: *** [lib] Error 2 gmake[2]: *** [all] Error 2 gmake[1]: *** [src] Error 2 make: *** [all] Error 2 Even if I try: [root@boppity-new freeradius-server]# echo 'BOILER=yes' >> Make.inc [root@boppity-new freeradius-server]# make Making all in src... Making all in src/include... gmake[4]: Nothing to be done for `all'. Making all in src/lib... CC dict.c gmake[4]: /usr/local/src/freeradius-server/libtool: Command not found gmake[4]: *** [dict.lo] Error 127 gmake[3]: *** [lib] Error 2 gmake[2]: *** [all] Error 2 gmake[1]: *** [src] Error 2 make: *** [all] Error 2 Am I being an idiot? Regards Scott Armitage
Scott Armitage wrote: gmake[4]: /usr/local/src/freeradius-server/libtool: Command not found gmake[4]: *** [dict.lo] Error 127 gmake[3]: *** [lib] Error 2 gmake[2]: *** [all] Error 2 gmake[1]: *** [src] Error 2 make: *** [all] Error 2
IIRC running libtoolize cleared this up. I'm not sure if that's the way things are supposed to work, or whether the build system should be setting LIBTOOL to the system installed path.
Brian Julin wrote:
IIRC running libtoolize cleared this up. I'm not sure if that's the way things are supposed to work, or whether the build system should be setting LIBTOOL to the system installed path.
Libtool has been shot. It will not be missed. I'm going to remove *entirely* all references to libtool && libltdl from the "master" branch. Alan DeKok.
On 13/09/12 14:03, Brian Julin wrote:
Scott Armitage wrote: gmake[4]: /usr/local/src/freeradius-server/libtool: Command not found gmake[4]: *** [dict.lo] Error 127 gmake[3]: *** [lib] Error 2 gmake[2]: *** [all] Error 2 gmake[1]: *** [src] Error 2 make: *** [all] Error 2
IIRC running libtoolize cleared this up. I'm not sure if that's the way things are supposed to work, or whether the build system should be setting LIBTOOL to the system installed path.
I think libtool is in the process of being removed from the tree because it's horrible and deserves to die. This is probably a result of that.
Scott Armitage wrote:
is anyone else having problems with using building FR3.0 I get the following: .. Am I being an idiot?
Nope. I've been using the new system in my sandbox, and didn't notice that the old system was borked. I've pushed some fixes. Both should work now from a default "configure". The next step is to make the new system the default. I'm also inclined to get rid of ALL references to libtool && jlibtool from the source. The downside is that you can no longer create statically linked versions of FreeRADIUS. Given that it's 2012, I'm not too worried about this. Alan DeKok.
participants (4)
-
Alan DeKok -
Brian Julin -
Phil Mayers -
Scott Armitage