Hi,
ok, Oops-1.5.18-2 is now running w/ db-2.7.7 on OpenBSD :>
Don't cry, the patch for *db* is rather short :]]
Oops is fine so far, since it was the problem of db-2.7.7 to detect
OpenBSD and it's mutex "stuff".
sleepycat really uses assembly locks, so it was only a problem of the
defines in configure.in to detect OpenBSD itself.
After successfully building db w/ mutexlocks, oops was happy to
initialize its storages also :-PP
db-2.7.7-sourcetree:
--- dist/configure.in.orig Wed Oct 10 22:26:08 2001
+++ dist/configure.in Wed Oct 10 23:10:45 2001
@@ -373,10 +373,10 @@
exit(1);}], [db_cv_spinlocks=mc68020/gcc])
fi
-dnl x86/gcc: BSD/OS, FreeBSD, NetBSD, Linux
+dnl x86/gcc: BSD/OS, FreeBSD, NetBSD, Linux, OpenBSD
if test "$db_cv_spinlocks" = no; then
AC_TRY_RUN([main(){
-#if defined(i386)
+#if defined(__i386__)
#if defined(__GNUC__)
exit(0);
#endif
I will now check, if I can find the problem about db-3.1.x ..
ciao
--
Philipp Buehler, aka fips | sysfive.com GmbH | BOfH | NUCH | <double-p>
#1: Break the clue barrier!
#2: Already had buzzword confuseritis ?
=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
Archive is accessible on http://lists.paco.net/oops-eng/
