You can make it permanent adding the command in ~/.bashrc *Jordi Soucheiron* Software Engineer
*DEXMA* Parc Tecnològic la Salle Sant Joan de la Salle, 42 08022 Barcelona t/f: [+34] 93 181 01 96 www.dexmatech.com jsouchei...@dexmatech.com 2010/7/22 Miriam Dali <miriamd...@yahoo.fr> > Thanks a lot for your answer, I tried to change the path variable as you > told me (export PATH=/opt/msp430-gcc-4.4.3/bin:$PATH) > , and it works only for one session. When I restart my session and I opened > another bash, I must repeat the same thing. Actually I don't need to move > the old one but to let the system see the path of the new version first. > Thanks a lot > Mir > > --- En date de : Lun 19.7.10, Przemek Klosowski < > przemek.klosow...@gmail.com> a écrit : > > De: Przemek Klosowski <przemek.klosow...@gmail.com> > Objet: Re: [Mspgcc-users] upgrade mspgcc > À: "GCC for MSP430 - http://mspgcc.sf.net"; < > mspgcc-users@lists.sourceforge.net> > Date: Lundi 19 juillet 2010, 14h27 > > On Mon, Jul 19, 2010 at 6:12 AM, Miriam Dali <miriamd...@yahoo.fr> wrote: > > > THank you for your responses, I try to install it > > ~/mspgcc4/build/gcc-4.4.3-build: make install > > but it doesn't overwrite the old version, msp430-gcc --version gives me: > > msp430-gcc (GCC) 3.2.3 > > When you call a command by a simple name (e.g. 'cmd') rather than a > full pathname (/usr/bin/cmd) the system locates it via the PATH > environment variable. Do 'which msp430-gcc' to see which actual > filename was found and executed---it will show the place where the old > version is installed. The new executable will be there in a place like > /usr/local/bin/msp430-gcc, and that path is probably mentioned in your > PATH but later than the path to the old executable, or not mentioned > at all. > > You can call your new executable by specifying its explicit > pathname---probably something like /usr/local/bin/msp430-gcc. If that > works, you could modify your PATH variable to have this location up > front; depending on where the new one is installed, it might be: > > export PATH=/usr/local/bin:$PATH > > Since you tried 'make install' I conclude that you don't plan to use > the old msp430-gcc, so you could find where it is and delete it > entirely. > If the old version was loaded as a package on your distribution (apt > for Debian/Ubuntu, RPM for Fedora/Redhat), just use rpm -e or apt; > otherwise you can do it manually but you'd have to be sure that you > find all the locations (binaries, libraries, etc) because there's > nothing as confusing as some old files being found and used by the new > installation. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > >
