Propeller GCC Linux Source Build Change

jazzed

Please note that the procedure for building Propeller GCC (the compiler, not user programs) on Linux and Mac OSX has changed.

Significantly, the default build will now use /opt/parallax as the target directory and users should put /opt/parallax/bin in their path.

It is possible to use the old /usr/local/propeller setup for builds by replacing the jbuild.sh PREFIX=/opt/parallax with the old PREFIX=/usr/local/propeller

A new Propeller GCC distribution will not be created because of this change.

For more information on building Propeller GCC, see: http://code.google.com/p/propgcc/wiki/PropGccBuild

David Betz

jazzed wrote: »

Please note that the procedure for building Propeller GCC (the compiler, not user programs) on Linux and Mac OSX has changed.

Significantly, the default build will now use /opt/parallax as the target directory and users should put /opt/parallax/bin in their path.

It is possible to use the old /usr/local/propeller setup for builds by replacing the jbuild.sh PREFIX=/opt/parallax with the old PREFIX=/usr/local/propeller

A new Propeller GCC distribution will not be created because of this change.

For more information on building Propeller GCC, see: http://code.google.com/p/propgcc/wiki/PropGccBuild

I've modified the new build process slightly to eliminate the need to edit jbuild.sh if you want to place Propeller GCC in a directory other than /opt/parallax. You can now do this by using the following command line:

PREFIX=/usr/local/propeller ./rebuild.sh

You can also do this if you want to build using more than one thread:

PREFIX=/usr/local/propeller ./jbuild.sh 4

This will build Propeller GCC using four threads.

Of course, you can replace /usr/local/propeller in the above examples with a directory of your choice but please make sure that you have write access to the target directory.