[Digikam-devel] [Bug 137747] New: Error in 'configure', when setting 'kdelibsuff'

Leandro Motta Barros lmb at stackedboxes.org
Wed Nov 22 22:29:50 GMT 2006

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
           Summary: Error in 'configure', when setting 'kdelibsuff'
           Product: digikam
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: lmb stackedboxes org

Version:           0.9.0-rc1 (using KDE KDE 3.5.1KDE 1.2)
Installed from:    Unlisted Binary PackageUnlisted Binary Package
OS:                Linux

I am getting some problem while running 'configure', before starting to actually compile DigiKam. This problem is happening in 0.9.0-rc1, but it also happened in the latest beta you released (0.9.0-beta3, or was it called 0.9.0-beta1-r3? Whatever...) Anyway, some time ago I sucessfuly compiled DigiKam 0.9.0-beta1-r1 on the same system, so I suppose this problem was introduced in the latest versions.

Actually, 'configure' doesn't really issue an error, it executes as if everything went right, but it sets some variable to an incorrect value, and this causes a compilation error afterwards.

I have tracked the problem to be around line 8310 (sorry, I made changes while looking for this, so I don't know the exact line number), where the variable 'kdelibsuff' is set. 'ldd conftest.out' produces the following output here:

$ldd conftest.out                                                 
        libc.so.6 => /System/Links/Libraries/libc.so.6 (0xb7df2000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7f23000)

and after running that monstruous 'sed', it is transformed to

        libc.so.6 => /System/Links/Libraries/libc.so.6 (0xb7e65000)

So, 'kdelibsuff' is being set to '        libc.so.6 => /System/Links/Libraries/libc.so.6 (0xb7e65000)', which is clearly wrong.

I don't understant that 'sed' command being used in 'configure', but perhaps it's being confused by the strange path where my libc is found. This path is not the usual one, but it is correct, given that the Linux distribution I use (www.gobolinux.org) uses a different file hierarchy (I more sensible one, I would say, but this is a bug report, not an advertisement ;-))

So, I think this is enough information, but feel free to contact me for any missing detail.

And thanks for the nice program :-)

More information about the Digikam-devel mailing list