-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John, Most of the boost libs compile, and even regex appears as though it's compiling... but when all is said and done, no binary library can be found in bin or bin-stage. During the compile, I do get a lot of messages like this: /usr/local/home/synic/downloads/boost-1.30.2/boost/regex/config.hpp:437: redefinition of `int isupper(int)' /usr/include/ctype.h:134: `int isupper(int)' previously defined here Thanks, Adam Olsen John Maddock wrote: |> Has anyone had any luck compiling boost_regex on OpenBSD 3.3? | | | I know that other BSD variants are supported OK: what problem are you | having (and does following the instructions for configuring Boost fix | them: see http://www.boost.org/libs/config/config.htm#config_script) | ? | | John. | | _______________________________________________ Boost-users mailing | list Boost-users@lists.boost.org | http://lists.boost.org/mailman/listinfo.cgi/boost-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/nVa0iTy1B31kxaoRAkDQAJ9/x6wKtzb05AvzlgcB1/GcFhNyFACePRD0 HNSeDW5XBKVw5rR8QBnCv+Y= =P0nW -----END PGP SIGNATURE-----

Most of the boost libs compile, and even regex appears as though it's compiling... but when all is said and done, no binary library can be found in bin or bin-stage.

During the compile, I do get a lot of messages like this:

/usr/local/home/synic/downloads/boost-1.30.2/boost/regex/config.hpp:437: redefinition of `int isupper(int)' /usr/include/ctype.h:134: `int isupper(int)' previously defined here

Looks like you need to comment out the following in boost/config/platform/bsd.hpp: // // The BSD has macros only, no functions: // #define BOOST_NO_CTYPE_FUNCTIONS If you're prepared to, can you: a) Download a cvs development snapshot from www.boost-consulting.com b) Build the latest bjam from this. c) cd into boost-root/status and run: bjam test 2>&1 | tee regress.log and let me have (by private email) the regress.log output file - that should give me enough information to figure out what to change for the next release. Thanks, John.