Opened 13 years ago

Closed 13 years ago

#33404 closed defect (fixed)

kdepimlibs4 4.8.0 Build failed Error: Status 1 encountered during build

Reported by: wpociengel@… Owned by: nerdling (Jeremy Lavergne)
Priority: Normal Milestone:
Component: ports Version: 2.0.4
Keywords: Cc: sharky@…
Port: kdepimlibs4

Description

While building digikam 2.5 I received the following error while building missing requirements:

NOTE: I have verified all dependencies have been built and are listed as installed

port install kdepimlibs4
--->  Computing dependencies for kdepimlibs4
--->  Building kdepimlibs4
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for kdepimlibs4 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kdepimlibs4/kdepimlibs4/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
Macpro dual quad core 2.8Ghz 14GB
OS X 10.5.8
xcode 3.1.2
Macports 2.0.4

Attachments (1)

main.log.zip (24.3 KB) - added by wpociengel@… 13 years ago.

Download all attachments as: .zip

Change History (5)

Changed 13 years ago by wpociengel@…

Attachment: main.log.zip added

comment:1 Changed 13 years ago by nerdling (Jeremy Lavergne)

Cc: snc@… removed
Keywords: kdepimlibs4 Leopard removed
Owner: changed from macports-tickets@… to snc@…
Status: newassigned

Hmm, which libical is being used here? Please move /Library/Frameworks/libical.framework out of there for the duration of the build: clean and try building again.

:info:build ld warning: in /Library/Frameworks//libical.framework/libical, file is not of required architecture

Looks like we have yet another library to protect against…

comment:2 Changed 13 years ago by wpociengel@…

Bingo!!

I had tried with moving the copy in my user library but not this one. When I did I got the build to run.

I then (leaving all alone) rebuilt digikam and it completed. Now to try testing things, but at least the build went well.

I test both with and without the library moved to see if there are any adverse effects but this is at least promising.

comment:3 Changed 13 years ago by wpociengel@…

No problems after compiling with the above library renamed. Everything seems to be working fine so the above workaround should help anyone else in a similar situation.

Thanks

comment:4 Changed 13 years ago by nerdling (Jeremy Lavergne)

Resolution: fixed
Status: assignedclosed

Added configure flags to KDE4-1.1 PortGroup r91715

Note: See TracTickets for help on using tickets.