Opened 14 years ago
Closed 14 years ago
#26439 closed defect (worksforme)
kdepim4 4.4.5 won't compile
Reported by: | dmbkiwi@… | Owned by: | nerdling (Jeremy Lavergne) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | sharky@…, bjoern.ricks@…, macports@…, mac.ports.fishspit@… | |
Port: | kdepim4 |
Description
kdepim4 fails to compile. This is the final output of sudo port -d install kdepim4:
cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdepim4/work/build/kresources/slox && /opt/local/bin/cmake -E cmake_symlink_library ../../lib/libkslox.4.4.0.dylib ../../lib/libkslox.4.dylib ../../lib/libkslox.dylib /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdepim4/work/build/CMakeFiles [ 16%] Built target kslox make: *** [all] Error 2 shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdepim4/work/build" && /usr/bin/make -j2 all " returned error 2 Error: Target org.macports.build returned: shell command failed DEBUG: Backtrace: shell command failed while executing "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" Warning: the following items did not execute (for kdepim4): org.macports.activate org.macports.build org.macports.destroot org.macports.install Log for kdepim4 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdepim4/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
Attachments (1)
Change History (11)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | sharky@… bjoern.ricks@… added |
---|---|
Keywords: | kdepim4 removed |
Milestone: | MacPorts 1.9.2 |
Owner: | changed from macports-tickets@… to snc@… |
Changed 14 years ago by dmbkiwi@…
Attachment: | main.log.zip added |
---|
comment:3 Changed 14 years ago by nerdling (Jeremy Lavergne)
Status: | new → assigned |
---|
comment:4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Ok, the relevant error from the main.log appears to be:
error: 'mem_fn' was not declared in this scope
Has duplicate #26532.
comment:6 Changed 14 years ago by macports@…
I have a build failure in kdepim4 as well due to mem_fn. It built fine on a 10.6 system (x86_64) but fails on my 10.5 system (ppc). I have looked briefly to see that there are at least a dozen files that use the mem_fn function but a third of those don't include boost/mem_fn.hpp. I must assume that in the cases where it is not directly included, then it is included through another header, but that the chain of includes is dependent on OS version or some other variable since it works on one machine and not the other. I do not have the time right now to dig deeper to figure out why.
comment:7 Changed 14 years ago by mac.ports.fishspit@…
I'm seeing a similar build failure, the same version of kdepim4 (4.4.5) compiled fine on my older machine which was a first gen Macbook Pro w/10.6 (x86), but I got a newer Macbook Pro (x86_64) recently and it fails with the same mem_fn error. Strangely it seems to get to different places in the code if I attempt to build it again after getting the error, but it never seems to get farther than about 90% complete.
comment:9 Changed 14 years ago by macports@…
after adding
#include <boost/mem_fn.hpp>
at the top of kdepim-4.4.5/kleopatra/crypto/gui/newresultpage.cpp I was able to compile kdepim4 successfully.
comment:10 Changed 14 years ago by nerdling (Jeremy Lavergne)
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
Please check if this is still an issue for whichever package it's now part of—kdepim didn't make it into 4.5 I think.
Please don't set the Milestone field for port tickets, but do Cc the port maintainers.
Please attach the main.log file, compressing it first if it is large; the output you provided is insufficient to know what went wrong.