Bug 627042 – =media-gfx/digikam-5.5.0 wont compile

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ladislav Zitka 2017-08-04 09:40:32 UTC]

There are appearing some reference errors while linking

[Comment 1 Ladislav Zitka 2017-08-04 09:42:28 UTC]

I cannot attach any file (emerge info output and build.log), it looks the site is having some problems....

[Comment 2 Ladislav Zitka 2017-08-04 09:56:15 UTC]

Created attachment 487894 [details]
Emerge info output

[Comment 3 Ladislav Zitka 2017-08-04 10:06:47 UTC]

Created attachment 487896 [details]
Emerge build log extract

[Comment 4 Ladislav Zitka 2017-08-04 10:07:05 UTC]

So, logs attached.

[Comment 5 Jonas Stein 2017-08-04 19:43:32 UTC]

Thank you for the report. Please attach the complete logfile
https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide#Report_a_build-time_bug_.28emerge_failed.29
and reopen this ticket (Status:unconfirmed).

You can check also, if there are libs which need to be rebuilt, or a broken gcc update. 

https://wiki.gentoo.org/wiki/Upgrading_GCC

[Comment 6 Ladislav Zitka 2017-08-05 10:41:19 UTC]

Created attachment 488002 [details]
Emerge full build log

I will also now rebuild all dependencies.

[Comment 7 Ladislav Zitka 2017-08-05 11:39:04 UTC]

I am running now emerge --emptytree digikam (just 500 packages..) on 32 thread system, so it will be fast, and switched from GCC 5.* to 7.1 before this action.

[Comment 8 Ladislav Zitka 2017-08-05 20:50:55 UTC]

Ok, still failing, but I have found reported error with specific version of cmake:
https://www.mail-archive.com/[e-mail]/msg156191.html

and relevant bug:
https://bugs.kde.org/show_bug.cgi?id=382703

So there was issue with my cmake 3.9(using latest from testing branch -> ~amd64) vs digikam.

I did dummy version bump by just increasing number to 5.6.0 and emerge without issues.

Thx Jonas for navigation.

[Comment 9 Andreas Sturmlechner 2017-08-05 23:08:38 UTC]

Thanks for investigating, upstream made sure to hide the fix under a meaningless commit message...

[Comment 10 Andreas Sturmlechner 2017-08-05 23:09:41 UTC]

Created attachment 488064 [details, diff]
digikam-5.5.0-cmake-3.9.patch

Could you please test the patch against digikam-5.5.0?

[Comment 11 Ladislav Zitka 2017-08-06 07:40:16 UTC]

Yes, will do test.

[Comment 12 Ladislav Zitka 2017-08-06 08:04:23 UTC]

I confirm that user patch works:
>>> Emerging (1 of 1) media-gfx/digikam-5.5.0::gentoo
 * digikam-5.5.0.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                                                                        [ ok ]
>>> Unpacking source...
>>> Unpacking digikam-5.5.0.tar.xz to /var/tmp/portage/media-gfx/digikam-5.5.0/work
>>> Source unpacked in /var/tmp/portage/media-gfx/digikam-5.5.0/work
>>> Preparing source in /var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core ...
 * Applying patches from /etc/portage/patches/media-gfx/digikam-5.5.0 ...
 *   digikam-5.05.0-cmake-3.9.patch ...                                                                                                                                                                             [ ok ]
 * User patches applied.

.......

....


* Messages for package media-gfx/digikam-5.5.0:

 * User patches applied.
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.

[Comment 13 Ladislav Zitka 2017-08-06 08:07:29 UTC]

Created attachment 488086 [details]
Version bump to 5.6.0

This is dummy version bump, in this version, the issue is already fixed upstream.

[Comment 14 Andreas Sturmlechner 2017-08-06 08:11:12 UTC]

(In reply to Ladislav Jech from comment #13)
> This is dummy version bump, in this version, the issue is already fixed
> upstream.

The bug report suggests otherwise. 5.6.0 is two months old, the fix is from two weeks ago - so if it worked for you, then out of pure chance.

Anyway, fix pushed in e53a832593d385ddf4e2c6304d2265488b0c16ca