On Sat, May 07, 2005, Ralf S. Engelschall wrote: > On Fri, May 06, 2005, David J. Bruce wrote: > > > I was recently attempting to build the sasl package using the > > 'with_sasldb' option on a solaris 10 system. I noticed however that > > configure was failing to find a working Berkeley DB library even though > > the db package was installed. (This is with OpenPKG 2.3-SOLID) > > > > It would appear that Berkeley DB has recently begun using the > > 'fdatasync' library function. On solaris this exists only within the > > realtime library (librt). > > > > Thus anything using Berkeley DB will require to be linked against librt > > on solaris. I've validated this by adding -lrt to the LIBS environment > > variable for the sasl build. This resulted in the sasldb functionality > > being present in the final package (as shown by saslpasswd2 and > > sasldblistusers2 being built). > > > > Off the top of my head, I can think of two ways to fix this; Either by > > adding librt to all the packages which build against db, or by fixing > > the berkeley DB package not to use fdatasync under solaris. > > > > What do you folks think would be preferable? Of course, I could be > > heading up the wrong garden path. > > There are already a bunch of packages which add -lrt to the LIBS > under Solaris 10, so although I personally do not like this > platform-specifics, it it ok to do also for SASL. Actually, exactly this > was already done in the OpenPKG-CURRENT "sasl" package a few weeks ago. > So, just use the OpenPKG-CURRENT "sasl" in the meantime. Or wait a few > hours, I'll MFC this back to OpenPKG 2.3, too.
Ok, now MFC'ed: sasl-2.1.20-2.3.1.src.rpm See also: http://cvs.openpkg.org/chngview?cn=23338 Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
