stan-dev / stan-dev/ci-scripts
Bleeding-edge: Actually build GCC from source
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 3
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
See how the official images do it:
https://github.com/docker-library/gcc/blob/915af5ccbb6b09575e244f280c26925e77172039/15/Dockerfile
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced official GCC image Dockerfile at https://github.com/docker-library/gcc/blob/915af5ccbb6b09575e244f280c26925e77172039/15/Dockerfile, then locate the corresponding build entry point in this repository. Done means the CI scripts build the bleeding-edge GCC from source as requested and the existing build workflow completes successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100