Installing multiple toolset versions
joel at OARcorp.com
Tue Oct 30 15:11:41 UTC 2001
Thomas Doerfler wrote:
> currently I need to work with two distinct toolset versions
> (gcc/binutil/newlib), since I am sharing my time between two
> projects based on different RTEMS versions (One is the
> PPC403/405 software splitup :-> )
> Up to now I have downloaded the "ready to run" RPMs for the
> toolsets but in my current situation I ran into problems,
> because at least the GCC package (powerpc-rtems-gcc-
> gcc2.95.3newlib1.9.0-1.i386.rpm) only works when installed in
> the default location (/opt/rtems/...), so there can only be
> one compiler package installed for a certain target
> architecture. Currently I use a different machine to install
> and run the second toolset, but this is not very nice...
I use three methods in house to manage this.
1. Another machine for the 4.5 branch testing.
2. Load the tools on a server and mount them for occasional use. Be
the server ends up knowing about the RPMS. I use this trick for
3rd machine temporarily without loading the tools there. I mount
the /opt/rtems from the trunk or 4.5 machine.
3. Remove one version of RPMs and install the other.
> Some years ago, when RPMs where not available, the tools per
> default were installed in a dedicated directory with a unique
> name like /usr/local/rtems/<gcc-version>-<binutil-version>-
> <newlib-version>. Wouldn't it be a good idea to fall back to
> such a naming scheme for future toolset RPMs? Then it would be
> possible to have multiple versions of a toolset installed on
> the same machine and multi-project maintenance would be much
> Any further opinions on that?
> IMD Ingenieurbuero fuer Microcomputertechnik
> Thomas Doerfler Herbststrasse 8
> D-82178 Puchheim Germany
> email: Thomas.Doerfler at imd-systems.de
> PGP public key available at: http://www.imd-
More information about the users