

gtk+ cannot be built for ppc64 anyway.I’ve been making my own Mac icons for folders, applications, and a myriad of other uses for well over 20 years now. Other packages like gimp, gutenprint, xsane, ufraw, gipm-app and so on did not require any further changes.Īlthough PowerMac G5 is ppc64, I've built everything ppc 32-bit. This '(null)' in warning seemed suspicious to me so I added another 'if' that checks for that case in glib's g_value_init() function. #7 0x0008b67c in gimp_rectangle_select_options_gui () #2 0x0124fce4 in g_object_new_internal () Reason: KERN_INVALID_ADDRESS at address: 0x44424414 Program received signal EXC_BAD_ACCESS, Could not access memory. (gimp-2.8:7170): GLib-GObject-WARNING : gvalue.c:183: cannot initialize GValue with type 'gchararray', the value has already been initialized as '(null)' It crashed right after splash screen with following backtrace: This seem to be more reasonable than applying one compilation policy over all compiled package. Instead of adding -faltivec, I rearranged inclusion of GTK/GDK files or renamed local variables (mostly from pixel to just p). I attached my changes to ports that I made to complete build of gimp 2.8.10 (quartz, no X!) on my old PowerMac G5.
#GIMP FOR MAC 10.5.8 PATCH#
I am not to familiar with other/newer CPU & OS requirements, so I am not too sure what conditions need to be put around the flag additions in the patch to make it work in all cases, but as it moves the decision to the compiler where it has already been coded, I guess it is better than repeating all that work in the Portfile.

My solution was to use the -Xarch option, which I think might be a better solution for the range of hardwares now needed to be supported.

OK, did not work for me on 10.5.8 Intel universal gcc 4.0.1 (build 5493) Not sure where I have gone wrong, perhaps something else needs setting, or configure is not doing the combination of PPC & i386 correctly. :info:configure checking whether we can compile AltiVec code. :info:configure checking whether /usr/bin/gcc-4.0 understands -faltivec. :info:configure configure: WARNING: The assembler does not support the MMX command set. :info:configure checking whether we can compile MMX code. :info:configure checking whether /usr/bin/gcc-4.0 understands -mmmx. :info:configure checking for socket in -lsocket. My main.log reports the following with or without the patch log file during configure, however there is the same errors at the end:. It looks to me that the complaint is over the declaration of "pixel", which I guess is the AltiVec pixel.Īnyway, the following difference stands out earlier in my. Just trying to get up to speed on it, have tried the patch to no effect. I too am hitting this problem, building on 10.5.8 Intel universal gcc 4.0.1 (Apple Inc.
#GIMP FOR MAC 10.5.8 CODE#
Somewhat surprisingly, the code compiles if I add -faltivec or -fno-altivec deps/gimpdrawable.Tpo -c -o gimpdrawable.o gimpdrawable.c

I././app -I././app -I/opt/local/include/cairo -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/libpng15 -D_REENTRANT -I/opt/local/include/gegl-0.2 -I/opt/local/include/babl-0.1 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -D_REENTRANT -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/libpng15 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/include -DGIMP_APP_VERSION=\"2.8\" -DG_LOG_DOMAIN=\"Gimp-Core\" -I/opt/local/include -DGIMP_DISABLE_DEPRECATED -DBABL_DISABLE_DEPRECATED -DGSEAL_ENABLE -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -pipe -O2 -arch ppc -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -Wmissing-format-attribute -Wformat-security -fno-common -MT gimpdrawable.o -MD -MP -MF. There was a similar altivec issue for gegl ( #35148) recently.įjelljo:~/var/macports/sources//graphics/gimp2/work/gimp-2.8.2/app/core $ /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I.
