Author: baggins                      Date: Mon Jun 25 15:52:07 2007 GMT
Module: SOURCES                       Tag: HEAD
---- Log message:
- removed Darwin bits from configure

---- Files affected:
SOURCES:
   ogle-cvs-20070625.patch (1.1 -> 1.2) 

---- Diffs:

================================================================
Index: SOURCES/ogle-cvs-20070625.patch
diff -u SOURCES/ogle-cvs-20070625.patch:1.1 SOURCES/ogle-cvs-20070625.patch:1.2
--- SOURCES/ogle-cvs-20070625.patch:1.1 Mon Jun 25 17:42:43 2007
+++ SOURCES/ogle-cvs-20070625.patch     Mon Jun 25 17:52:02 2007
@@ -2629,33 +2629,6 @@
  sparc)
        if test "x$GCC" = xyes; then
          O_CFLAGS="$O_CFLAGS -mcpu=ultrasparc -mvis"
-@@ -738,10 +833,25 @@
- powerpc|ppc)
-       if test "x$GCC" = xyes; then
-         O_CFLAGS="$O_CFLAGS -fomit-frame-pointer -funroll-loops"
-+
-+dnl On MacOS X with Apple's gcc3.3, -mcpu=7400 and -faltivec is used.
-+dnl We assume that no other version of gcc is used in darwin
-+
- dnl is the right? needed? use just -m7400 ? need new gcc for that..
- dnl is there a -mcpu -march flag that we should use?
- dnl should be a try compile on this line.. 
--        XCFLAGS="-Wa,-m7400"
-+
-+dnl What are correct options for altivec on other platforms/os/gcc versions?
-+        case "$host_os" in
-+        darwin*)
-+              XCFLAGS="-mcpu=7400 -faltivec -O3"
-+dnl Apples gcc3.3 only understands 'old' motorola-style altivec asm.
-+              USE_ALTIVEC_DARWIN=yes
-+              ;;
-+        *)
-+              XCFLAGS="-Wa,-m7400"
-+              ;;
-+        esac
- dnl that sets USE_ALTIVEC depending on the success
-         USE_ALTIVEC=yes
-       fi
 @@ -775,6 +885,19 @@
    BUILD_MMX=1
    CFLAGS="$CFLAGS $XCFLAGS"
================================================================

---- CVS-web:
    http://cvs.pld-linux.org/SOURCES/ogle-cvs-20070625.patch?r1=1.1&r2=1.2&f=u

_______________________________________________
pld-cvs-commit mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

Reply via email to