[Bug 70935] New: BerkelyDB setup fails in configure script

[Michael Satterwhite]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=70935     
           Summary: BerkelyDB setup fails in configure script
           Product: kdevelop
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: satterwh at weblore.com


Version:           3.0.0 Beta 2 (using KDE KDE 3.1.1)
Installed from:    SuSE RPMs
OS:          Linux

Although a similar problem was reported and marked resolved, this problem has been recurring in the forum. When trying to do ./configure with KDevelop 3 Beta 2, configure will fail if the BerkelyDB is in any non-standard location - and an fresh install of the BerkelyDB from their site will put it in an non-standard location. This occurs even if the location is specified with --with-extra-includes and --with-extra-libs.

The problem is that by the time the check for the BerkelyDB is done, the CXXFLAGS variable has no references to the include or library directories (for verification, dump this variable at line 36070 in the configure script). Without this reference, it will not be able to find the BerkelyDB - even though it is correctly on the system.

A workaround for this problem is to apply the following patch:

36068a36069,36074
> #The KDevelop configure script does not take into account
> #the --with-extra-includes or --with-extra-libs flag. This
> #may cause the check for software to fail. To chech for
> #the Berkely DB, add these flags back in now
>
> CXXFLAGS="$CXXFLAGS $all_includes $all_libraries"

Note that I have not checked for any other required components that may be affected by the loss of the include / library references, which is why I consider it a workaround rather than a fix. It does, however, correct the problem with the BerkelyDB.