[bind10-dev] how to build boost libraries on FreeBSD and MacOS X

Jelte Jansen jelte at isc.org
Tue Mar 23 19:35:34 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/23/2010 07:27 PM, JINMEI Tatuya / 神明達哉 wrote:
>>
>> Currently it'll fail during build (for --without-boost-lib because it
>> naively included 'libno' now,
> 
> Is this true?  From a quick look at configure.ac it doesn't seem to be
> possible.  I actually tried building it --without-boost-python, but no
> Makefile has '-lno'.
> 

well it does here:

(i can easily fix them btw, but i wanted to know first what it is we
should do)

jelte at dragon:~/repos/bind10/trunk> svn up
At revision 1634.
jelte at dragon:~/repos/bind10/trunk> ./configure --without-boost-system
jelte at dragon:~/repos/bind10/trunk> make
<snip>
libtool: link: g++ -g -O2 -g -Wall -Wextra -Wwrite-strings
- -Woverloaded-virtual -Wno-sign-compare -fPIC -o b10-auth auth_srv.o
main.o  -L/usr/lib/python3.1/config
../../../src/lib/auth/.libs/libauth.a
../../../src/lib/dns/.libs/libdns.a
../../../src/lib/config/.libs/libcfgclient.a ../../../src/lib/cc/libcc.a
../../../src/lib/exceptions/.libs/libexceptions.a /usr/lib/libsqlite3.so
../../../src/lib/xfr/.libs/libxfr.a
main.o: In function `__static_initialization_and_destruction_0':
/home/jelte/repos/bind10/trunk/src/bin/auth/../../../ext/boost/system/error_code.hpp:205:
undefined reference to `boost::system::get_system_category()'
<etc>

jelte at dragon:~/repos/bind10/trunk> ./configure --without-boost-lib
jelte at dragon:~/repos/bind10/trunk> make
<snip>
/bin/bash ../../../libtool --tag=CXX   --mode=link g++  -g -O2 -g -Wall
- -Wextra -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -fPIC
- -Lno -L/usr/lib/python3.1/config      -o b10-auth auth_srv.o main.o
../../../src/lib/auth/.libs/libauth.a
../../../src/lib/dns/.libs/libdns.a
../../../src/lib/config/.libs/libcfgclient.a ../../../src/lib/cc/libcc.a
../../../src/lib/exceptions/.libs/libexceptions.a -lsqlite3
../../../src/lib/xfr/.libs/libxfr.a -lboost_system-mt
../../../libtool: line 4992: cd: no: No such file or directory
libtool: link: cannot determine absolute directory name of `no'
make[5]: *** [b10-auth] Error 1

this one's also wrong, but we can do that at the same time:

jelte at dragon:~/repos/bind10/trunk> ./configure --with-boost-lib
jelte at dragon:~/repos/bind10/trunk> make
<snip>
/bin/bash ../../../libtool --tag=CXX   --mode=link g++  -g -O2 -g -Wall
- -Wextra -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -fPIC
- -Lyes -L/usr/lib/python3.1/config      -o b10-auth auth_srv.o main.o
../../../src/lib/auth/.libs/libauth.a
../../../src/lib/dns/.libs/libdns.a
../../../src/lib/config/.libs/libcfgclient.a ../../../src/lib/cc/libcc.a
../../../src/lib/exceptions/.libs/libexceptions.a -lsqlite3
../../../src/lib/xfr/.libs/libxfr.a -lboost_system-mt
../../../libtool: line 4992: cd: yes: No such file or directory
libtool: link: cannot determine absolute directory name of `yes'


>> and for --without-boost-system it'll fail
>> with unresolved symbols), which is certainly wrong.
> 
> In any case, I agree this is wrong.  My intent when I introduced
> --with-boost-system and --with-boost-python was that it should be
> at least buildable either with or without these features.
> 
> Of course, the bigger question remains:
> 
>> Are we making boost libs mandatory? If so, should we remove all
>> non-boostlib usage from the source? (while i'm wary of having this
>> run-time dependency added, esp. on something as changeable as boost, i'd
>> love to get all the ifdefs out if they're not absolutely completely
>> necessary)
> 
> I share your concerns.  It's probably time to consider acceptable
> level of dependency toward the production-ready version.
> 

See my somewhat longer mail from earlier today about what I think our
options are :)

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkupGAYACgkQ4nZCKsdOncU9FwCgttLnEJp2MevfMfBTx8gYWEr9
mfQAoNT8Hg0jGtB7q+IEAwrDK44c5nJZ
=9jli
-----END PGP SIGNATURE-----



More information about the bind10-dev mailing list