Date: Tue, 15 May 2012 12:51:56 -0400 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: Heimdal 1.5.2 problem Message-ID: <CA%2BQLa9Bs1VSBoMW0cHvSSeET=9X7F--33iv=860FzKv%2BHYuqNg@mail.gmail.com> In-Reply-To: <9880B4F2567E41A582B6B9DA178AECFD@black> References: <CA%2BQLa9ArX15Cgtyq%2B7PhhXtGGOj1dtVM4pisGfkFzVDJE7cs8A@mail.gmail.com> <4FAD492C.3060807@gmx.de> <CA%2BQLa9CyVUmvy=NzHiP73iTTRKVqU9Eza=PPMmLZrogoUn_gAg@mail.gmail.com> <CA%2BQLa9AC_mDrBiPaYOJ_M3F%2Bq07aUV1TATJcFgxSKCr2gPOFWw@mail.gmail.com> <9880B4F2567E41A582B6B9DA178AECFD@black>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 15, 2012 at 5:46 AM, Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au> wrote: > Thanks for the updates Robert. > > I've pursued building heimdal on a custom FreeBSD9-Stable jail built with= out > crypto (openssl, heimdal,...); and forced the selection of bdb throughout= the > range 5 to 41 via the following ports.conf setting > > *: WITH_BDB_VER=3D5 > ... > *: WITH_BDB_VER=3D41 > Combined with > security/heimdal: PREFIX=3D/usr/local | WITH_CRACKLIB | WITHOUT_SQLITE | = WITH_BDB > > Only the databases/db41 builds heimdal to completion. =A0All others termi= nated > with > > ------------------------ > > /var/ports/usr/ports/security/heimdal/work/heimdal-1.5.2/lib/com_err/.lib= s/libc > om_err.so /usr/local/lib/libintl.so /usr/local/lib/libiconv.so > /var/ports/usr/ports/security/heimdal/work/heimdal-1.5.2/lib/roken/.libs/= librok > en.so ../../lib/sqlite/.libs/libheimsqlite.so ../../lib/roken/.libs/libro= ken.so > -lcrypt /usr/local/lib/libldap.so /usr/local/lib/libsasl2.so -lssl -lcryp= to > /usr/local/lib/liblber.so -ldb =A0-O2 -O2 -march=3Dprescott -mtune=3Dpres= cott > -Wl,--version-script -Wl,./version-script.map -pthread =A0 -pthread -Wl,-= soname > -Wl,libhdb.so.11 -o .libs/libhdb.so.11 > .libs/db3.o: In function `hdb_db_create': > db3.c:(.text+0x3a): multiple definition of `hdb_db_create' > .libs/db.o:db.c:(.text+0x15): first defined here > *** Error code 1 > ------------------------ > > There was a change to /usr/ports/security/heimda/files with the addition = of > patch patch-cf__db.m4, which I removed during one build attempt with db41= . This > generated many more error messages > > ------------------------ > libtool: compile: =A0cc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../i= nclude > -I../../lib/roken -I../../lib/roken -I../asn1 -I./../asn1 -I/usr/local/in= clude > -DHDB_DB_DIR=3D\"/var/db/heimdal\" -I./../krb5 -I../../lib/sqlite > -I/usr/local/include -I/usr/local/include/db41 -D_LARGE_FILES=3D -Wall > -Wmissing-prototypes -Wpointer-arith -Wbad-function-cast -Wmissing-declar= ations > -Wnested-externs -O2 -pipe -pipe -O2 -g0 -ggdb0 -DSTRIP_FBSDID -UDEBUGGIN= G > -UEBUGGING -I/usr/local/include/db41 -DLDAP_DEPRECATED -fno-strict-aliasi= ng -MT > db.lo -MD -MP -MF .deps/db.Tpo -c db.c =A0-fPIC -DPIC -o .libs/db.o > db.c: In function 'DB_close': > db.c:48: error: too few arguments to function 'd->close' > db.c: In function 'DB_lock': > db.c:67: error: too few arguments to function 'd->fd' > db.c: In function 'DB_unlock': > db.c:80: error: too few arguments to function 'd->fd' > db.c: In function 'DB_seq': > db.c:104: error: 'DB' has no member named 'seq' > ... > ------------------------ > > Unfortunately this confirms that the heimdal 1.5.2 port doesn't build wit= h bdb. > I'll advise later in the week, the result of my preferred build of heimda= l over > ldap (over bdb5). > > For completeness, FreeBSD9-Stable was updated yesterday (May 14) and the = ports > tree was also updated and built on a virgin machine today (May 15). Yep. That's exactly what I've found. Also, as I have noted earlier, if you look at the output from configure during the building of the heimdal port, it builds db41 as a dependency, but configure does not find it! The only version of BDB that configure finds is the one in the base OS which is 185! This port is totally borken as far as building with BDB backend support. I've reached out to the Heimdal mailing list for some assistance, and I will try to fix the problem myself and submit a patch to the port. I haven't been able to get the port maintainer to respond to queries about this problem, but he may just be very busy.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9Bs1VSBoMW0cHvSSeET=9X7F--33iv=860FzKv%2BHYuqNg>