-
Notifications
You must be signed in to change notification settings - Fork 17
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.
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
Building PropGCC on systems with GCC6 or GCC7 #77
Comments
I'm building PropGCC using Guix with GCC5. With Guix you can also get older GCC toolchains. |
I'm curious about this too. It looks like this project hasn't been updated in a while and doesn't build with recent GCC versions. Is propgcc no longer supported? |
"Supported" is a poorly defined word. It's come up many times on the Parallax forums... no answer (that I recall) has been given by a Parallax employee (that was sufficient enough to be memorable). In order to build PropGCC on my CI server, I built a Docker image with all the necessary tools. See my thread here: https://forums.parallax.com/discussion/168418/building-propgcc-with-docker |
Raspbian9 has a gcc-4.6 package, so it can build the gcc-4.6 based propgcc only additionally needing an old texinfo4. On Debian9 the easiest way to get the old gcc-4.6 based propgcc compiled is to build an ancient texinfo4 and gcc-4.9.4 first (e.g. to live in /opt/xyzzy) and then build propgcc with it. Probably using @DavidZemon's builds is the most efficient way to get propgcc but yes... I know... there are always some individualists who insist in baking their own binaries @home... ;-) ...me too! Building the gcc-6 based propgcc is easier on PCs but there was a problem building it natively on Raspbian. I forgot where I have my notes about it... |
What is needed to get PropGCC built on systems with GCC6 or GCC7?
Did noone do this successfully so far?
Is everyone still using the permian binaries from the days when the typical average Linux system came with GCC4?
The text was updated successfully, but these errors were encountered: