Bug 353580

Summary:	iconutil: error: Unsuported image format
Product:	[Applications] kblackbox	Reporter:	R. Hamilton <rlhamil>
Component:	general	Assignee:	Nicolas Roffet <nicolas-kde>
Status:	REPORTED ---
Severity:	normal	CC:	kde-games-bugs-null, niederstrasser
Priority:	NOR
Version First Reported In:	0.4
Target Milestone:	---
Platform:	MacPorts
OS:	macOS
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description R. Hamilton 2015-10-05 22:46:09 UTC

iconutil on El Capitan (OS X 10.11) seems to require strict input file names that begin with "icon_" prefix.  Following describes this:
http://stackoverflow.com/questions/31632304/iconseterror-failed-to-generate-icns/32490491#32490491

The first few lines of the MacPorts build log starting with the error:
:info:build [  0%] Built target kblackbox_automoc
:info:build /Applications/Xcode.app/Contents/Developer/usr/bin/make -f CMakeFiles/kblackbox.dir/build.make CMakeFiles/kblackbox.dir/depend
:info:build make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build'
:info:build [  2%] Generating kblackbox_SRCS.icns
:info:build /usr/bin/iconutil --convert icns --output /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.icns /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset
:info:build error: Unsuported image format
:info:build error: Unsuported image format
:info:build error: Unsuported image format
:info:build error: Unsuported image format
:info:build error: Unsuported image format
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset:warning: Missing image for variant named 'icon' resource error: 'Failed to load image at 128@2x.'.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset:warning: Missing image for variant named 'icon' resource error: 'Failed to load image at 256@1x.'.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset:warning: Missing image for variant named 'icon' resource error: 'Failed to load image at 256@2x.'.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset:warning: Missing image for variant named 'icon' resource error: 'Failed to load image at 512@1x.'.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset:warning: Missing image for variant named 'icon' resource error: 'Failed to load image at 512@2x.'.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset:error: Variant named 'icon' contains no image resources.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kblackbox/kblackbox/work/build/kblackbox_SRCS.iconset:error: Failed to generate ICNS.
:info:build make[2]: *** [kblackbox_SRCS.icns] Error 1


Reproducible: Always

Steps to Reproduce:
1.on El Capitan, run "port install kblackbox"
2.
3.

Actual Results:  
build failed

Expected Results:  
build should have succeeded

If the fix for qt4-mac on El Capitan hasn't been incorporated yet, one might need manual intervention to get that prerequisite to install, as described here:
https://trac.macports.org/ticket/48129

This ticket corresponds to MacPorts ticket https://trac.macports.org/ticket/49106

Comment 1 Justin Zobel 2021-03-09 06:30:03 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.