10.0-CUR r226986 && ports/security/cyrus-sasl2-saslauthd

Matthias Apitz guru at unixarea.de
Fri Nov 4 05:03:06 UTC 2011

El día Thursday, November 03, 2011 a las 01:42:50PM -0400, b. f. escribió:

> No, it is not the same.  You can either masquerade, by setting UNAME_r
> and OSVERSION, or by editing the headers and scripts that define them;
> or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE
> (which is implied by USE_AUTOTOOLS and GNU_CONFIGURE).  Right now the
> masquerading is probably safer, because there are some problems with
> the fix that are still being resolved -- and a few ports that may fail
> despite the fix.  But of course if you help to test without
> masquerading, these problems will be resolved sooner.

the ports/security/cyrus-sasl2-saslauthd does not install with
WITH_FBSD10_FIX; terminates with:

cc  -O2 -pipe -fno-strict-aliasing  -rpath=/usr/lib:/usr/local/lib -o
mechanisms.o auth_dce.o  auth_getpwent.o auth_krb5.o  auth_krb4.o
auth_pam.o aut
h_rimap.o  auth_httpform.o auth_shadow.o  auth_sia.o auth_sasldb.o lak.o
dap.o cache.o cfile.o  krbtf.o utils.o ipc_unix.o  ipc_doors.o
md5.o -L/usr/lib -lgssapi -lheimntlm -lkrb5 -lhx509 -lcom_err -lcrypto
-lasn1 -l
roken -lcrypt  -lcrypt   ../sasldb/.libs/libsasldb.al -lpam
cc: ../sasldb/.libs/libsasldb.al: No such file or directory
*** Error code 1

installes fine with UNAME_r set to 9-CURRENT;


Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru at unixarea.de> - w http://www.unixarea.de/
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5

More information about the freebsd-current mailing list