On Sun, Aug 24, 2008 at 12:03:32AM +0200, Matthias Kilian wrote:
> On Fri, Aug 22, 2008 at 10:50:17AM -0400, Brad wrote:
> > The following diff eliminates the AltiVec FLAVOR and enables
> > it by default for PowerPC packages. I need someone to test
> > the AltiVec operation ona G4 system. Load the Gimp in a xterm
> > with "gimp --verbose" and within the first couple of lines
> > of verbose output it will list the supported SIMD instructions
> > and it should show +altivec.
>
> Nope, I still get -altivec, and it looks like
> gimp_cpu_accel_get_support() isn't called at all.
>
> I'm now rebuilding with this additional patch:
Now that I have had time to look at this a bit more it turns out
that at the moment the framework and little bits of code for AltiVec
in the Gimp are not actually enabled.
Here is the appropriate diff for now..
Index: Makefile
===================================================================
RCS file: /cvs/ports/graphics/gimp/stable/Makefile,v
retrieving revision 1.35
diff -u -p -r1.35 Makefile
--- Makefile 12 Jul 2008 13:28:04 -0000 1.35
+++ Makefile 24 Aug 2008 00:53:35 -0000
@@ -3,7 +3,7 @@
COMMENT= GNU Image Manipulation Program
DISTNAME= gimp-2.4.6
-PKGNAME= ${DISTNAME}p1
+PKGNAME= ${DISTNAME}p2
SHARED_LIBS= gimp-2.0 246.00 \
gimpbase-2.0 246.00 \
gimpcolor-2.0 246.00 \
@@ -56,23 +56,12 @@ MODULES= devel/gettext \
USE_X11= Yes
USE_GMAKE= Yes
USE_LIBTOOL= Yes
-
AUTOCONF_VERSION= 2.61
-
CONFIGURE_STYLE= autoconf
CONFIGURE_ARGS= ${CONFIGURE_SHARED}
CONFIGURE_ARGS+=--without-gtkhtml2 --without-librsvg --without-print \
--without-gnomevfs --without-libcurl --disable-python
CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include/libpng -I${LOCALBASE}/include
-I${X11BASE}/include" \
LDFLAGS="-L${LOCALBASE}/lib -L${X11BASE}/lib"
-
-FLAVORS= altivec
-FLAVOR?=
-
-.if ${FLAVOR:L} == "altivec"
-ONLY_FOR_ARCHS= powerpc
-.else
-CONFIGURE_ARGS+= --disable-altivec
-.endif
.include <bsd.port.mk>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
