#14705 closed enhancement (fixed)
Misc changes to install guide
Reported by: | jdemeyer | Owned by: | mvngu |
---|---|---|---|
Priority: | major | Milestone: | sage-5.10 |
Component: | documentation | Keywords: | |
Cc: | Merged in: | sage-5.10.rc2 | |
Authors: | Jeroen Demeyer | Reviewers: | Jean-Pierre Flori |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
See patch.
Attachments (1)
Change History (14)
comment:1 Changed 8 years ago by
comment:2 Changed 8 years ago by
- Status changed from new to needs_review
comment:3 Changed 8 years ago by
Should we recommend GNU make 3.82?
comment:4 follow-up: ↓ 5 Changed 8 years ago by
W.r.t. Clang, I'd mention that Sage's GCC currently won't build with it [either], because of #13948 (but a couple if not most of Sage's packages already do, and help in getting the remaining ones to build is welcome).
comment:5 in reply to: ↑ 4 Changed 8 years ago by
Replying to leif:
W.r.t. Clang, I'd mention that Sage's GCC currently won't build with it [either], because of #13948 (but a couple if not most of Sage's packages already do, and help in getting the remaining ones to build is welcome).
My changes add the sentences "Clang currently does not work." and "Clang is currently not supported, see :trac:12426
." I think that's clear enough, and it points to #12426 where further details can be found.
comment:6 follow-up: ↓ 7 Changed 8 years ago by
It may indeed be worth suggesting to use GNU make 3.82 if possible.
Other than that I'm happy with the patch.
Just out of curiosity, what's the definitive reason for dropping OpenSolaris? support? We only have one intermittent patchbot and there is no upstream anymore?
comment:7 in reply to: ↑ 6 Changed 8 years ago by
Replying to jpflori:
We only have one intermittent patchbot.
Mostly this. It became impossible to test. And people have asked before about dropping OpenSolaris support.
Changed 8 years ago by
comment:8 follow-up: ↓ 12 Changed 8 years ago by
OK, made some further changes, needs_review.
I also bumped the space requirement to 5 GB, since I just noticed my full Sage 5.10 install (for testing) takes 4.2 GB of disk space.
comment:9 Changed 8 years ago by
- Reviewers set to Jean-Pierre Flori
- Status changed from needs_review to positive_review
Great, you also added/changed the RAM requirement which I just thought about (I could build Sage on a Raspberry Pi with just 256 MB of RAM and 512 MB of swap).
comment:10 Changed 8 years ago by
- Merged in set to sage-5.10.rc2
- Resolution set to fixed
- Status changed from positive_review to closed
comment:11 Changed 8 years ago by
I'd still have clarified that currently even bootstrapping Sage's GCC with Clang doesn't work (out of the box), but for a subtle reason (with a link to that ticket).
Related, it's also unclear what exactly is meant by "a wide variety of compilers is supported", i.e., whether they're supported in the sense that Sage can bootstrap its own GCC with these, or whether they're really able to build Sage.
Something for Sage 5.11.* ...
comment:12 in reply to: ↑ 8 ; follow-up: ↓ 13 Changed 8 years ago by
Replying to jdemeyer:
I also bumped the space requirement to 5 GB, since I just noticed my full Sage 5.10 install (for testing) takes 4.2 GB of disk space.
Somebody^{TM} should investigate why...
Not that long ago, 2 - 2.5 GB were indeed sufficient (without clones and the like).
(And while we've added some spkgs, we also dropped some, like MoinMoin and Twisted.)
comment:13 in reply to: ↑ 12 Changed 8 years ago by
Replying to leif:
Replying to jdemeyer:
I also bumped the space requirement to 5 GB, since I just noticed my full Sage 5.10 install (for testing) takes 4.2 GB of disk space.
Somebody^{TM} should investigate why...
$SAGE_LOCAL
takes 1.9 GBdevel/sage/build
takes 1.4 GB of stuff which (I believe) is only temporary and not really neededdevel/sage/doc/output
takes 0.6 GBspkg/standard
takes 0.3 GB
Looks good to me.