Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-1479

Search for Berkeley DB doesn't find current version

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • all
    • 0.33
    • install
    • None

    Description

      After installing the latest released version of Berkeley DB 
      (BerkeleyDB.4.1), the configure tool for subversion
      doesn't find it in the default location.
      
      configure searches:
      
      checking for built-in Berkeley DB... no
      checking for Berkeley DB in the standard places (as db4)... no
      checking for Berkeley DB in the standard places (as db)... no
      checking for Berkeley DB in /usr/local/include/db4 and /usr/local/lib (as 
      db4)... no
      checking for Berkeley DB in /usr/local/include/db4 and /usr/local/lib (as 
      db)... no
      checking for Berkeley DB in /usr/local (as db4)... no
      checking for Berkeley DB in /usr/local (as db)... no
      checking for Berkeley DB in /usr/local/BerkeleyDB.4.0 (as db4)... no
      checking for Berkeley DB in /usr/local/BerkeleyDB.4.0 (as db)... no
      checking for Berkeley DB in /usr/include/db4 and /usr/lib (as db4)... no
      checking for Berkeley DB in /usr/include/db4 and /usr/lib (as db)... no
      
      Berkeley DB is installed in:
      
      /usr/local/BerkeleyDB.4.1
      
      by default. All permissions are set correctly (755) for directories
      by DB make install.
      
      Resolution: Search path(s) need to be updated to search for DB.4.x
      instead of DB.4.0 alone.
      on 17-aug-03
      

      Original issue reported by gregben

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              subversion-importer Subversion Importer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: