Opened 13 years ago

Closed 10 years ago

#7645 closed defect (invalid)

'set -e' used inappropriately in python-2.6.2.p4

Reported by: David Kirkby Owned by: Georg S. Weber
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: William Stein, Mike Hansen Merged in:
Authors: Reviewers: Jeroen Demeyer
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


The following is one more example of where trying to build Sage on an uncommon platform (HP-UX) discovers bugs which affect all platforms. This is yet one more justification of why it is desirable to POSIX compatible portable code and check Sage on many platforms.

As you can see below, python does not build on my HP C3600 running HP-UX 11i, but we have no clue whatsoever why. Normally Sage would give some clue, but here there is none.

Finished extraction
Host system
uname -a:
HP-UX hpbox B.11.11 U 9000/785 2016698240 unlimited-user license
CC Version
gcc -v
Using built-in specs.
Target: hppa1.1-hp-hpux11.11
Configured with: /tmp/gcc-4.3.3.tar.gz/gcc-4.3.3/configure --host=hppa1.1-hp-hpux11.11 --target=hppa1.1-hp-hpux11.11 --build=hppa1.1-hp-hpux11.11 --prefix=/opt/hp-gcc-4.3.3 --with-gnu-as --without-gnu-ld --enable-threads=posix --enable-languages=c,c++ --with-gmp=/proj/opensrc/be/hppa1.1-hp-hpux11.11 --with-mpfr=/proj/opensrc/be/hppa1.1-hp-hpux11.11
Thread model: posix
gcc version 4.3.3 (GCC) 

real	0m0.111s
user	0m0.050s
sys	0m0.040s
sage: An error occurred while installing python-2.6.2.p4

The reason no error message is generated, is due to the inappropriate use of

set -e

in the spkg-install script. The package python-2.6.2.p4 has in spkg-install

# This tells Bash to exit the script if any statement returns 
# a non-true value.
set -e


cp patches/ src/Lib/ctypes/
if [ $? -ne 0 ]; then
    echo "Error copying patched ctypes"
    exit 1

cp patches/ src/Lib/
if [ $? -ne 0 ]; then
    echo "Error copying patched"
    exit 1

It should be noted that 'set -e' causes any failure to result in the script exiting immediately with a non-zero exit code. Since the script has exited, no further processing takes place - even the code which checks for an error!

I've cc'ed the ticket to Mike and William, as they are listed as package maintainers.


Change History (3)

comment:1 Changed 10 years ago by Jeroen Demeyer

Milestone: sage-5.10sage-duplicate/invalid/wontfix
Reviewers: Jeroen Demeyer
Status: newneeds_review

Old version, no longer relevant.

comment:2 Changed 10 years ago by Jeroen Demeyer

Status: needs_reviewpositive_review

comment:3 Changed 10 years ago by Jeroen Demeyer

Resolution: invalid
Status: positive_reviewclosed
Note: See TracTickets for help on using tickets.