#14172: mpir-2.6.0.p0 fails to build on Intel "Core" CPUs
------------------------------------------------------------------+---------
       Reporter:  tmonteil                                        |         
Owner:  GeorgSWeber
           Type:  defect                                          |        
Status:  new        
       Priority:  major                                           |     
Milestone:  sage-5.8   
      Component:  build                                           |    
Resolution:             
       Keywords:  mpir spkg ABI standard Intel Core               |   Work 
issues:             
Report Upstream:  Reported upstream. Developers acknowledge bug.  |     
Reviewers:             
        Authors:                                                  |     Merged 
in:             
   Dependencies:                                                  |      
Stopgaps:             
------------------------------------------------------------------+---------

Comment (by leif):

 Replying to [comment:9 tmonteil]:
 > Here are the files.

 Thanks.

 > - /proc/cpuinfo is at http://paste.debian.net/237897/
 > - spkg/build/mpir-2.6.0.p0/src/config.log is at
 http://paste.debian.net/237898/
 > - spkg/build/mpir-2.6.0.p0/src/config.guess is at
 http://paste.debian.net/237899/

 Sorry, I meant the output of running `config.guess` (you uploaded the file
 itself), but I guess it is just `core-pc-linux-gnu`.  (Its output would
 also be interesting for MPIR 2.4.0, although I doubt it'll differ.)

 [[BR]]

 > I will see if i can found a log for the sage 5.6 build somewhere.

 If you still have the Sage 5.6 installation (but not the logs in
 `spkg/logs/`), you could try reinstalling MPIR 2.4.0 with `./sage -f -s
 spkg/standard/mpir-2.4.0.p6.spkg`. (`-s` keeps the spkg build directory,
 where the source code (including `config.guess`) and `config.log` are
 located, even if no error occurred during the installation.)

 [[BR]]

 > Note that is is sometimes good to be able to build a 32-bits sage system
 on a 64-bits machine. For example, i need this when building sage for a
 live USB key that aims to boot on a widest range of machines.

 Yes.  Some also prefer 32-bit versions for virtual machines (on 64-bit
 machines).

 The safest way to produce (32-bit) binary dists is still to create them
 natively, on old machines.  (E.g., `ECM_CONFIGURE=--disable-sse2` is
 currently necessary for Pentium III and some older CPUs, which I only
 noticed while actually building on a Pentium III ...)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14172#comment:10>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to