Changes between Version 1 and Version 3 of Ticket #11107


Ignore:
Timestamp:
04/01/11 05:44:59 (2 years ago)
Author:
drkirkby
Comment:

I checked and found bzip2 is the only package with this bug, so I have updated the description to reflect this.

Dave

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11107

    • Property Status changed from new to needs_review

  • Ticket #11107 – Description

    v1 v3  
    11I discovered this after trying to debug a Linux installation. 
    22 
    3 The bzip2 package (in particular the file {{{$SAGE_ROOT/spkg/base/bzip2-1.0.5-install}}}) handles SAGE64 in a different way to the vast majority (if not all) other packages. It has: 
     3The bzip2 package (in particular the file {{{$SAGE_ROOT/spkg/base/bzip2-1.0.5-install}}}) handles SAGE64 in a different way to the all other packages. It has: 
    44 
    55{{{ 
    … …  
    3030 
    3131This would 
    32  * Be consistent with most if not all other packages.  
     32 * Be consistent with all other packages.  
    3333 * Work on any platform, which might be useful on some like AIX 
    3434 * Could help debug some Linux issues if Linux is building 32-bit. (I found this useful to help someone on sage-support) 
    3535 * Avoids two calls to {{{uname}}}  
    36  * Allows any flag to be used for building 64-bit executable, not just the one use by Sun/Oracle compilers and GCC. Commerical compilers for both AIX and HP-UX use different flags.  
     36 * Allows any flag to be used for building 64-bit executable, not just the one use by Sun/Oracle compilers and GCC. Commercial compilers for both AIX and HP-UX use different flags.  
    3737 * Would allow any flags set by the user in CFLAGS to override those here. However, currently setting CFLAGS globally in Sage can not be considered a good idea, but that's a more general bug and well outside the scope of this ticket.  
    3838