Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change the sage build system to use "set -e" so that if any error occurs in spkg-install then the build immediately terminates with an error #6598

Closed
williamstein opened this issue Jul 23, 2009 · 2 comments
Closed

Change the sage build system to use "set -e" so that if any error occurs in spkg-install then the build immediately terminates with an error #6598

williamstein opened this issue Jul 23, 2009 · 2 comments
Labels
c: build r: invalid t: bug

Comments

@williamstein
Copy link
Contributor 

> Nonetheless, we should be checking the error code after every line
> executes, one way or another.  Is there a way to automatically do this
> in bash?

"set -e" should do it.

Google brings up this page, besides lots of others:

http://www.davidpashley.com/articles/writing-robust-shell-scripts.html


Cheers,
Burcin

CC: @dimpase @jhpalmieri

Component: build

Issue created by migration from https://trac.sagemath.org/ticket/6598
@williamstein williamstein added this to the sage-5.11 milestone Jul 23, 2009
@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@mkoeppe
Copy link
Contributor

mkoeppe commented Aug 30, 2020

comment:5

outdated, can be closed

@mkoeppe mkoeppe removed this from the sage-6.4 milestone Aug 30, 2020
@jhpalmieri
Copy link
Member

comment:6

Okay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: build r: invalid t: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@williamstein @jhpalmieri @jdemeyer @fchapoton @mkoeppe