digikam: build error in imagehistorygraph_boost.h

[juer_gen01@…]

I tried several times to install digikam. + I uninstalled and cleaned it one try: I uninstalled "all" .. failed - searching similar tickets I found #29223 --> but "sudo port sync" did not fix the problem either: ok, I got some updates, but finally the installation failed again:

$ sudo port install digikam
--->  Computing dependencies for ImageMagick
--->  Fetching archive for ImageMagick
--->  Attempting to fetch ImageMagick-6.7.4-0_0+q16.darwin_11.x86_64.tbz2 from http://packages.macports.org/ImageMagick
--->  Fetching ImageMagick
--->  Attempting to fetch ImageMagick-6.7.4-0.tar.xz from http://lil.fr.distfiles.macports.org/ImageMagick
--->  Verifying checksum(s) for ImageMagick
--->  Extracting ImageMagick
--->  Configuring ImageMagick
--->  Building ImageMagick
--->  Staging ImageMagick into destroot
--->  Installing ImageMagick @6.7.4-0_0+q16
--->  Cleaning ImageMagick
--->  Computing dependencies for ImageMagick
--->  Deactivating ImageMagick @6.7.3-1_0+q16
--->  Cleaning ImageMagick
--->  Activating ImageMagick @6.7.4-0_0+q16
--->  Cleaning ImageMagick
--->  Computing dependencies for net-snmp
--->  Fetching archive for net-snmp
--->  Attempting to fetch net-snmp-5.7.1_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/net-snmp
--->  Fetching net-snmp
--->  Verifying checksum(s) for net-snmp
--->  Extracting net-snmp
--->  Applying patches to net-snmp
--->  Configuring net-snmp
--->  Building net-snmp
--->  Staging net-snmp into destroot
--->  Installing net-snmp @5.7.1_1
--->  Cleaning net-snmp
--->  Computing dependencies for net-snmp
--->  Deactivating net-snmp @5.7.1_0
--->  Cleaning net-snmp
--->  Activating net-snmp @5.7.1_1
--->  Cleaning net-snmp
--->  Computing dependencies for digikam
--->  Building digikam
Error: Target org.macports.build returned: shell command failed (see log for details)
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
$ 

another try:

$ sudo port install digikam
Password:
--->  Computing dependencies for digikam
--->  Building digikam
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for digikam is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_digikam/digikam/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
$ 

Can you give me a hint, what to do? Thanks and regards Jürgen

[ryandesign (Ryan Carsten Schmidt)]

The relevant error in your log is:

no matching function for call to ‘target(const boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int>&, const boost::reverse_graph<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, boost::property<boost::vertex_index_t, int, boost::property<vertex_properties_t, Digikam::HistoryVertexProperties, boost::no_property> >, boost::property<edge_properties_t, Digikam::HistoryEdgeProperties, boost::no_property>, boost::no_property, boost::listS>, const boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, boost::property<boost::vertex_index_t, int, boost::property<vertex_properties_t, Digikam::HistoryVertexProperties, boost::no_property> >, boost::property<edge_properties_t, Digikam::HistoryEdgeProperties, boost::no_property>, boost::no_property, boost::listS>&>&)’

#29223 has nothing at all to do with this.

[ryandesign (Ryan Carsten Schmidt)]

Well, #29223 has nothing to do with it, assuming you did at some point "sudo port clean digikam" and then try again, but I now realize the output you've shown above does not show that. Please clean digikam and try again. If it fails again, attach the new main.log.

[juer_gen01@…]

main.log after cleaning and re-installing digikam

[juer_gen01@…]

Replying to ryandesign@…:

Well, #29223 has nothing to do with it, assuming you did at some point "sudo port clean digikam" and then try again, but I now realize the output you've shown above does not show that. Please clean digikam and try again. If it fails again, attach the new main.log.

Hi, thanks for the investigation. - Yes, your assumption is correct.
To create a "clean log file" for the new investigation, now I cleaned digikam, tried to re-install it (similar result) and added the main.log to the ticket. Hope you can see more now ...
regards Jürgen

[ryandesign (Ryan Carsten Schmidt)]

I assume this is an incompatibility with the latest version of boost 1.48.0, and that updating digikam to the latest version 2.4.1 will help.

[juer_gen01@…]

Replying to ryandesign@…:

I assume this is an incompatibility with the latest version of boost 1.48.0, and that updating digikam to the latest version 2.4.1 will help.

To be honest:

• what does that mean to me?
  
• What should I do to skip the error & to get digikam to run?

[ryandesign (Ryan Carsten Schmidt)]

It means you could use howto/InstallingOlderPort to install boost 1.47.0 and see if digikam builds then. I know it used to build; I have it installed on my system right now. Or you can wait awhile and either the maintainer or I will test and commit the update to 2.4.1. I am starting to work on it now, but it may be a day or two before I reach a conclusion, because it takes a long time to build, and I will have to build it multiple times, and I also have other things to do in the mean time.

[juer_gen01@…]

terminal output of boost try

[juer_gen01@…]

Replying to ryandesign@…:

It means you could use howto/InstallingOlderPort to install boost 1.47.0 and see if digikam builds then. I know it used to build; I have it installed on my system right now. Or you can wait awhile and either the maintainer or I will test and commit the update to 2.4.1. I am starting to work on it now, but it may be a day or two before I reach a conclusion, because it takes a long time to build, and I will have to build it multiple times, and I also have other things to do in the mean time.

Thanks for the Explanation!
as a newbee (@macports, not @computers ;-) it's not too easy to get it all right here .. I think I found the related port (browser:trunk/dports/devel/boost/Portfile?rev=80816​)
and got it down to my disk, could start the installation, but the fetch failed

-->    :debug:fetch Fetching failed:: The requested URL returned error: 404

see attached log files "main.log_boost.txt" + "boost_fetch_failed.txt"
Since it it not too urgent to me, I think I'll follow your 2nd proposal to wait, until the new build is finished. Thanks for your effort + time
best regards, Jürgen

[ryandesign (Ryan Carsten Schmidt)]

patch to update to 2.4.1 that does not compile for me

[ryandesign (Ryan Carsten Schmidt)]

Attached is a patch to update digikam to 2.4.1. Unfortunately it fails with the same error. I'll leave this matter to the maintainer now.

My patch simply removes the CMakeLists.txt patch that had allegedly dealt with not installing the docs unless the +docs variant was used. In fact, the list of files installed by digikam is identical whether or not the +docs variant is used so I hope it's safe to just remove this patch.

In fact I see now that the code that was in the Portfile has a typo: it checks if [variant_isset doc] but the variant the portgroup adds is actually called "docs" not "doc". Perhaps this needs to be kept and the typo fixed.

I verified that digikam 2.1.1 builds fine with boost 1.47.0. Perhaps 2.4.1 would as well.

The logs you attached show you forgot to download boost's patchfiles from the repository as well and put them in a "files" directory next to the Portfile.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #32604.

[mail@…]

Same problem here. If it helps, I was able to build digiKam @2.1.1_1 successfully with Boost @1.46.1_0.

[stealthjeff@…]

Cc Me!

[stealthjeff@…]

Same problem on OSX/10.7 w/ xcode 4.2.1. Also with apple-gcc and llvm-gcc.

[ryandesign (Ryan Carsten Schmidt)]

Right. It's not a compiler problem. It's an incompatibility between digikam and the latest version of boost. The developers of digikam will need to fix this. Feel free to alert them to the problem.

[juer_gen01@…]

Replying to ryandesign@…:

Right. It's not a compiler problem. It's an incompatibility between digikam and the latest version of boost. The developers of digikam will need to fix this. Feel free to alert them to the problem.

Dear all,
thanks for your effort!
I informed them , please see ​http://www.digikam.org/drupal/node/638#comment-20158
Best regards
Jürgen

[gsking1@…]

FYI - looks like a patch to fix this issue in digikam has been prepared. Here: ​https://bugs.kde.org/show_bug.cgi?id=287772 ​http://commits.kde.org/digikam/d18ea6da2d3e2359f4113e83c3fd40c18a29ddab

[juer_gen01@…]

Replying to gsking1@…:

FYI - looks like a patch to fix this issue in digikam has been prepared. Here: ​https://bugs.kde.org/show_bug.cgi?id=287772 ​http://commits.kde.org/digikam/d18ea6da2d3e2359f4113e83c3fd40c18a29ddab

hm, still something wrong.
after "selfupdate" and "upgrade outdated" I did "sudo port install digikam" with the result "Error: Target org.macports.build returned: shell command failed (see log for details)"
see attached logs "update.txt", "install.txt" and "main.3.log"

[ryandesign (Ryan Carsten Schmidt)]

That's because nobody has fixed the problem in the MacPorts digikam port yet.

[juer_gen01@…]

Replying to ryandesign@…:

That's because nobody has fixed the problem in the MacPorts digikam port yet.

-- oops! thanks + sorry ;-)

[ryandesign (Ryan Carsten Schmidt)]

Attached is a patch to update to 2.5.0, which still does not build for me.

[ryandesign (Ryan Carsten Schmidt)]

r89258

[apyule]

Replying to ryandesign@…:

r89258

Thanks

[jgosmann (Jan Gosmann)]

Replying to ryandesign@…:

r89258

Thanks!

Actually, I planned to commit a fix and update to Digikam 2.5 this weekend myself. But I was holding back, because Digikam crashes at startup. But that's better than not building at all, I guess. Probably I have to report it as bug upstream, because I have no clue what is causing the problem.

Does anyone else have problems starting Digikam or is everything running fine?

btw: I am sorry that I was not able to do any updates of the port the last few months. Unfortunately, I had no spare time at my hand to do this.

[ryandesign (Ryan Carsten Schmidt)]

Ah yes. For me (on Snow Leopard x86_64) digikam opens, lets me get through the initial setup assistant, displays the Tip of the Day window with the buttons drawn but no tip text displayed, and then crashes.

[apyule]

I'm on Snow Leopard x86_64 too but digikam now runs perfectly for me.

[ryandesign (Ryan Carsten Schmidt)]

Had you used digikam before, and if so had you already turned off the Tip of the Day feature?

[apyule]

I had used digikam before, but tip of the day is on and working.

[juer_gen01@…]

Replying to jan@…:

Replying to ryandesign@…:

r89258

Thanks!

Actually, I planned to commit a fix and update to Digikam 2.5 this weekend myself. But I was holding back, because Digikam crashes at startup. But that's better than not building at all, I guess. Probably I have to report it as bug upstream, because I have no clue what is causing the problem.

Does anyone else have problems starting Digikam or is everything running fine?

btw: I am sorry that I was not able to do any updates of the port the last few months. Unfortunately, I had no spare time at my hand to do this.

Hi,
I'm on Lion, installation "finished" (after selfupdate, upgrade outdated), but digikam does not start at all. can't find a "crash log" below ~/Library/Logs/DiagnosticReports/ but in system area I found:

Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: digikam(3110)/KSharedDataCache: Unable to find an appropriate lock to guard the shared cache.  This *should* be essentially impossible. :( 
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: digikam(3110)/KSharedDataCache: Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. 
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: digikam(3110)/KSharedDataCache: Unable to unmap shared memory segment 0x10ff9a000 
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: digikam(3110)/kdeui (kdelibs): Session bus not found 
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: To circumvent this problem try the following command (with Linux and bash) 
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: export $(dbus-launch) 
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: KCrash: Application 'digikam' crashing...
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: KCrash: Attempting to start  from kdeinit
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: Warning: connect() failed: : No such file or directory
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: KCrash: Attempting to start  directly
Jan 23 10:21:57 laeppy [0x0-0x83083].digikam[3110]: KCrash failed to exec(), errno = 2
Jan 23 10:21:57 laeppy com.apple.launchd.peruser.504[175] ([0x0-0x83083].digikam[3110]): Exited with code: 253

other applications in kde-folder (dngconverter, showfoto,..) don't start either.

[gsking1@…]

Cc Me!

[gsking1@…]

I have the same crash as noted below. This is a new install of digikam and macports. The last thing I see before crash is the Tip of the Day window. Any ideas?

Replying to ryandesign@…:

Ah yes. For me (on Snow Leopard x86_64) digikam opens, lets me get through the initial setup assistant, displays the Tip of the Day window with the buttons drawn but no tip text displayed, and then crashes.

[jgosmann (Jan Gosmann)]

I reported the bug (with my console output of Digikam) upstream, now: ​https://bugs.kde.org/show_bug.cgi?id=292522

[jgosmann (Jan Gosmann)]

The bug has been tackled upstream and I submitted an update to the new version in ticket #34819. This ticket can be closed, I believe.

[ryandesign (Ryan Carsten Schmidt)]

r94162.

[juer_gen01@…]

hi & sorry, it still crashes (at least on my "lion" mac) see attached log files ;-(

regards juergen

[jgosmann (Jan Gosmann)]

The original build problem of this ticket is fixed. That's a new problem and unfortunately I do not know what's causing it. Digikam is working with my "lion" mac.

You could try what is described in this comment: comment:ticket:30578:7 If that doesn't help, I would ask you to report this problem upstream in the KDE bug tracker.