From owner-freebsd-questions Tue Oct 10 4:21:23 2000 Delivered-To: freebsd-questions@freebsd.org Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98]) by hub.freebsd.org (Postfix) with ESMTP id 00FAA37B66D for ; Tue, 10 Oct 2000 04:21:18 -0700 (PDT) Received: from wp2 (wp2 [192.168.0.12]) by osiris.ipform.ru (8.11.0/8.11.0) with SMTP id e9ABL3b06170 for ; Tue, 10 Oct 2000 15:21:10 +0400 (MSD) (envelope-from matrix@ipform.ru) Message-ID: <008b01c032ac$3128e020$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: References: <000501c0328d$afacf860$a20a140a@bfs.phone.com> Subject: DB_File building on FreeBSD (libdb in libc problem) Date: Tue, 10 Oct 2000 15:21:02 +0400 Organization: IP Form MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Here is what i got from DB_File developer on the problem with libdb. I wonder, if i can try this harmlessly. ----- Original Message ----- From: "Paul Marquess" To: "Artem Koutchine" Cc: Sent: Tuesday, October 10, 2000 11:42 AM Subject: RE: DB_File building on FreeBSD > Hi Artem, > > as it happens I have a partial solution that will allow DB_File to be built > with Berkeley DB 3.x on systems with an infected libc. I intend including > instructions once I've finalised the details. > > In the meantime, here is a summary of what you need to do. > > You are going to have to rebuild & install Perl from scratch to get this to > work. Untar a fresh copy of the perl source. Edit Configure and find the > line: > > libswanted='sfio socket inet nsl nm ndbm gdbm dbm db malloc dl' > > change it to this: > > libswanted='sfio socket inet nsl nm malloc dl' > > If you then build, test & install Perl as normal. > > You should now have a Perl that doesn't contain a reference to Berkeley DB. > > Now build DB_File as a stand-alone module. > > Paul > > > -----Original Message----- > > From: Artem Koutchine [mailto:matrix@ipform.ru] > > Sent: 06 October 2000 13:35 > > To: paul.marquess@btinternet.com > > Subject: DB_File building on FreeBSD > > > > > > Hello! > > > > I am having hard time building DB_File perl module on > > FreeBSD 4.x because FreeBSD has Berkeley DB built in libc > > and it is 1.85 and i want to use BDB 3.x or at least 2.x > > I can install BDB 3.x easily on the host. libdb3 is in the place, > > but DB_File continues to link against the old bdb and uses only > > 1.85. > > > > Did people contact you before on this matter and how to resolve > > the conflict? > > > > In case you need it, here is the full story: > > > > Given: > > db file created with 2.7.0 os Linux Slackware > > FreeBSD 4.1.1-stable with 1.85 included in libc > > perl 5.005_03 on FreeBSD host > > DB_File which comes with perl > > > > Need to accomplish: > > read that db file on FreeBSD host > > > > Problems: > > cannot read that db file on FreeBSD host > > > > Solution: > > install db 2.7.7 from ports > > install DB_File 1.73 from CPAN (supposed to support db up to 3.x) > > try to build DB_File linked agains the 2.7.7 version of DB: > > 1) perl Makefile.PL complains: > > Note (probably harmless): No library found for -ldb > > 2) try a little hack and make a link from db2 to db > > still 'Note (probably harmless): No library found for -ldb' > > 3) hell with it, open generate Makefile, add -ldb2 to LDFLAGS > > make > > make test > > make install > > try to open the - no luck , which means db lib is still taken from > > libc > > > > I do not understand how to make DB_File use db 2.7.7 instead of 1.85 > > built in in > > libc. > > > > Result: > > somebody needs to do something about it > > > > > > Regards, > > Artem > > > > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message