This package also depends on the packages on that list, to make it easy to have the build-essential packages installed.
Major decisions about GCC are made by the steering committee, guided by the mission statement.
For questions related to the use of GCC, please consult these web pages and the GCC manuals.
The only way to mitigate these exploits as a user of Raspbian is to keep your software up to date, as the upstream repositories track CVEs closely and try to mitigate them quickly.
The second reason, which is related to the first, is that the software you are running on your device most certainly contains bugs.
If you wish to try upgrading a Jessie image to Stretch, we strongly recommend making a backup first — we can accept no responsibility for loss of data from a failed update.
To upgrade, first modify the files If moving to a new Pi model (for example the Pi 3B ), you may also need to update the kernel and the firmware using the instructions above.
However, there are occasional changes made in the Foundation's Raspbian image that require manual intervention, for example a newly introduced package.
These are not installed with an upgrade, as this command only updates the packages you already have installed.
We strive to provide regular, high quality releases, which we want to work well on a variety of native and cross targets (including GNU/Linux), and encourage everyone to contribute changes or help testing GCC.