[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: configure fails on Solaris 2.8

From: <leif.eriksen_at_hpa.com.au>
Date: 2003-08-21 05:03:35 CEST

Well, in the configure stage, autoconf actually compiles and runs hundreds
(anyone actually know the number, it must be huge) of little
scripts/programs and the exe's that result, in order to test all kinds of
system functionality. And in your case, the system can build the little
piece of code trying to workout your BDB version (because it can find the
headers etc), but, alas, it cannot find the BDB shared lib it needs in order
to run the exe it has built.

And configure then burst into a logical inferno.

If you look in the config.log, I think you'll find your answer.

Perhaps the fail message should indicate this - but then again, any failure
in configure means a game of hunt the wumpus in config.log

Leif Eriksen
Developer

HPA
Direct: 03 9217 5600
Fax: 03 9217 5702

www.hpa.com.au <http://www.hpa.com.au>

-----Original Message-----
From: Dmitri Priimak [mailto:priimak@stanford.edu]
Sent: Thursday, August 21, 2003 12:55 PM
To: Leif Eriksen
Cc: dev@subversion.tigris.org
Subject: Re: configure fails on Solaris 2.8

Hi Leif.

Should this me mentioned somewhere in INSTALL file or I missed it.
I don't think that it should be required for LD_LIBRARY_PATH to be set
for build. It may be nessesary for running, but not compilation.

leif.eriksen@hpa.com.au wrote:
> I had this and I think I had to make sure the LD_LIBRARY_PATH had the path
> to my newly installed BDB 4.1
>
> Leif Eriksen
> Developer
>
> HPA
> Direct: 03 9217 5600
> Fax: 03 9217 5702
>
> www.hpa.com.au <http://www.hpa.com.au>
>
>
>
> -----Original Message-----
> From: Dmitri Priimak [mailto:priimak@stanford.edu]
> Sent: Thursday, August 21, 2003 11:36 AM
> To: dev@subversion.tigris.org
> Subject: configure fails on Solaris 2.8
>
>
> Hi All.
>
> I was trying to build svn version 0.27.0 on Solaris and got into problem.
> Running ./configure --with-berkeley-db=/usr/local/BerkeleyDB.4.1
> I get at some point:
>
> neon configured properly
> checking for any extra libraries neon needs...
> checking for static Apache module support... no
> checking for Apache module support via DSO through APXS... found at
> /usr/local/apache2/bin/apxs
> checking httpd version... recent enough
> checking for socket in -lsocket... yes
> checking for Berkeley DB in /usr/local/BerkeleyDB.4.1 (as db4)... no
> checking for Berkeley DB in /usr/local/BerkeleyDB.4.1 (as db)... no
> configure: error: Could not find Berkeley DB 4.0.14 with names: db4 db
>
> Same works on Linux. Both machines have /usr/local/BerkeleyDB.4.1 and do
> not have anywhere file libdb4.so
>

-- 
Dmitri Priimak
---------------
"Sages do not grieve for the living nor the dead." - Bhagavatgita.
**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are
addressed.  If you received this e-mail in error, please notify
the HPA Postmaster, postmaster@hpa.com.au, then delete 
the e-mail.
This footnote also confirms that this e-mail message has been swept for
the presence of computer viruses by MimeSweeper.  Before opening or
using any attachments, check them for viruses and defects.
Our liability is limited to resupplying any affected attachments.
HPA collects personal information to provide and market our services.
For more information about use, disclosure and access see our Privacy
Policy at www.hpa.com.au
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 21 05:04:33 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.