configure failure os x

Matthias Andree matthias.andree at gmx.de
Sat Apr 5 01:12:46 CEST 2003


"Michael K. Ter Louw" <mterlo1 at uic.edu> writes:

> I forgot to mention, I tried cc and c89 and neither setting would enable
> configure to finish successfully.  gcc appears to be there, running 'gcc'
> returns 'gcc: No input files'.  Bogofilter's configure would successfully
> compile some small programs using gcc, but would cause an error when
> compiling the BerkeleyDB test app (which is just a simple call to
> db_create() and then exit).  I have a feeling that BerkeleyDB's configure
> detected some kind of multi-threading support on this system, and then
> enabled it, causing anything that linked to BerkeleyDB to require the
> threading dependency to be resolved (which, to my knowledge, could only be
> done by using the xlc_r compiler).

Manually adding the required libraries should also work, xlc_r is just
an alias for xlc with some options (to use the c_r library and to define
some "REENTRANT" symbols) set.

> Maybe this could have been worked
> around by configuring Berkeley with --without=pthread or something...

BerkeleyDB likely chose posixmutexes for aix, and therefore
required pthreads. We can have configure find out if -lpthread or
-lthread are needed, or override cc to xlc_r on AIX. I've not yet
decided what is the best way, unfortunately, because I don't have an
account on an AIX machine that I could test on.

As you're writing in your other mail that BerkeleyDB might be the
problem, I will for now assume that the thread safety in question is
necessary on some systems because it usually has reentrancy as a side
effect. I'll try to look closer at the FreeBSD and Solaris builds of BDB
to figure.

-- 
Matthias Andree




More information about the Bogofilter mailing list