#11297: altivec must be disabled for ECL on PPC OSX 10.5
-----------------------+----------------------------------------------------
   Reporter:  dimpase  |          Owner:  GeorgSWeber                           
   
       Type:  defect   |         Status:  needs_review                          
   
   Priority:  blocker  |      Milestone:  sage-4.7                              
   
  Component:  build    |       Keywords:  PPC, MacOSX 10.5, ECL                 
   
Work_issues:           |       Upstream:  Reported upstream. Little or no 
feedback.
   Reviewer:           |         Author:                                        
   
     Merged:           |   Dependencies:                                        
   
-----------------------+----------------------------------------------------
Changes (by dimpase):

 * cc: kcrisman (added)
  * status:  new => needs_review


Old description:

> ECL 11.1.1.p0 spkg does not build on MacOSX PPC (G4) running MacOSX 10.5,
> and using XCode 3.1.4 (the lastest XCode for this platform).
> Symptoms: a crash half-way the build, at the log point
> {{{
> ;;; About to load cmp/load.lsp
> ;;;
> ;;; Now we are in shape to do something useful.
> ;;; End of bare.lsp
> }}}
> it can be:
> {{{
> Internal or unrecoverable error in:
> not a lisp data object
>   [2: No such file or directory]
> }}}
> or
> {{{
> Detected access to an invalid or protected memory address.
> Available restarts:
> 1. (CONTINUE) Ignore signal
> }}}
> or
> {{{
> 64 is an illegal index to "Variable in COMMON-LISP package:
> The last-but-one top-level forme".
> No restarts available.
> }}}
> or perhaps something else like this. This is apparently due to an ECL bug
> having to do with altivec instructions.
> Configuring with
> {{{
> ./configure CFLAGS="-mno-altivec -mabi=no-altivec"
> }}}
> makes the ECL build OK. See
> https://groups.google.com/group/sage-
> devel/browse_thread/thread/55313fb49133b97/8cbd9ac8826ef685#8cbd9ac8826ef685
>
> for more info on this.

New description:

 ECL 11.1.1.p0 spkg does not build on MacOSX PPC (G4) running MacOSX 10.5,
 and using XCode 3.1.4 (the lastest XCode for this platform).
 Symptoms: a crash half-way the build, at the log point
 {{{
 ;;; About to load cmp/load.lsp
 ;;;
 ;;; Now we are in shape to do something useful.
 ;;; End of bare.lsp
 }}}
 it can be:
 {{{
 Internal or unrecoverable error in:
 not a lisp data object
   [2: No such file or directory]
 }}}
 or
 {{{
 Detected access to an invalid or protected memory address.
 Available restarts:
 1. (CONTINUE) Ignore signal
 }}}
 or
 {{{
 64 is an illegal index to "Variable in COMMON-LISP package:
 The last-but-one top-level forme".
 No restarts available.
 }}}
 or perhaps something else like this. This is apparently due to an ECL bug
 having to do with altivec instructions.
 Configuring with
 {{{
 ./configure CFLAGS="-mno-altivec -mabi=no-altivec"
 }}}
 makes the ECL build OK. See
 https://groups.google.com/group/sage-
 devel/browse_thread/thread/55313fb49133b97/8cbd9ac8826ef685#8cbd9ac8826ef685

 for more info on this.

 The new spkg is at
 http://boxen.math.washington.edu/home/dima/packages/ecl-11.1.1.p1.spkg

 tested OK on MacOSX 10.5 PPC (and on few non-PPC systems just to make sure
 it's OK).
 Needs testing on more MacOSX PPC systems.

--

Comment:

 Replying to [comment:4 jdemeyer]:
 > I think having an argument CFLAGS and a conflicting environment variable
 CFLAGS is asking for touble.  Why not simply do

  {{{
  if [ "`uname -sm`" = "Darwin Power Macintosh" ] ; then
      CFLAGS="$CFLAGS -mno-altivec -mabi=no-altivec"
      export CFLAGS
  fi
 }}}
 >
 OK, I've created an spkg with this patch (link in the ticket description).

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11297#comment:7>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to