Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure
(a) For a ticketing approach, might be better to create tickets on the sourceforge project instead of emailing everybody with each one. Though I don't know if anybody's going to maintain the how-to for the existing mspgcc infrastructure; my preference is to leave packaging to downstream and just provide the patches. (b) Not sure what the last problem was; the failure to find msp430-ar? Probably you installed binutils in a directory that is not in your PATH. sudo can contribute to confusion there, since the path it uses is not the same as the path you've got in your main shell; contrast msp430-ar -v with sudo msp430-ar -v (c) You might be better off using mspgcc4 until we get the two projects back together. Run the buildgcc.pl script it comes with. Peter On Wed, Aug 11, 2010 at 5:43 PM, Errol errol.kow...@gmail.com wrote: Being a newbie to this, I wasn't sure if each problem should be treated as something unique, or part of the wider picture. I opted for the former, and more of a ticketing approach. Please accept my humblest apologies for erring on the wrong side. However, that said, the last (unanswered) problem has, in my opinion, little to do with typos, and the source code build, and more likely the compiler I'm using in my Ubuntu Jaunty installation. This one is the show stopper. Anyone got any ideas? - regards, Errol Kowald ^ Engenia Pty Ltd, 2 Clear St., Palmerston, ACT 2913, Australia pH:+612 6242 0351 ^ On Wed, 2010-08-11 at 16:00 -0400, John Porubek wrote: (hope no-one is too put-out by my pedantic nit picking) I've got no problems with the nit-picking, but I am a little put off by small changes to each subsequent Subject line so that each message shows up as the start of a new thread (instead of being properly nested as a single thread). Hope no one is too put off by my curmudgeonly response, John -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure
Thanks for your help Peter. I didn't realise that the root PATH would be different to the user PATH, so after trying to learn how to work around that, I took you advice, at (c), and tried building mspgcc4, from the procedure at http://mspgcc4.sourceforge.net/ What could go wrong? It's only 3 lines. :- ~$ svn checkout https://mspgcc4.svn.sourceforge.net/svnroot/mspgcc4 checked out revision 139 ~$ cd mspgcc4 ~/mspgcc4$ sh buildgcc.sh accepted all of the default choices started the build right now with the result :- Selected GCC 3.2.3 GDB version: 7.0.1 Insight version: 6.8-1 Target location: /opt/msp430-gcc-3.2.3 Binary package name: msp430-gcc-3.2.3_gdb_7.0.1.tar.bz2 - Do you want to start build right now? (y/n) [n] y Running sh do-binutils.sh /opt/msp430-gcc-3.2.3 2.20.1 http://ftp.uni-kl.de; build === makeinfo is missing from path, but required for the binutils build. Please install texinfo. Aborting. === sh do-binutils.sh /opt/msp430-gcc-4.4.3 2.20.1 http://ftp.uni-kl.de; build exited with status code 1. Failed to execute sh do-binutils.sh /opt/msp430-gcc-4.4.3 2.20.1 http://ftp.uni-kl.de; build at ./buildgcc.pl line 247, STDIN line 9. Where is makeinfo? What should PATH= ? What should the root PATH= ? Errol On Wed, 2010-08-11 at 18:08 -0500, Peter Bigot wrote: (a) For a ticketing approach, might be better to create tickets on the sourceforge project instead of emailing everybody with each one. Though I don't know if anybody's going to maintain the how-to for the existing mspgcc infrastructure; my preference is to leave packaging to downstream and just provide the patches. (b) Not sure what the last problem was; the failure to find msp430-ar? Probably you installed binutils in a directory that is not in your PATH. sudo can contribute to confusion there, since the path it uses is not the same as the path you've got in your main shell; contrast msp430-ar -v with sudo msp430-ar -v (c) You might be better off using mspgcc4 until we get the two projects back together. Run the buildgcc.pl script it comes with. Peter On Wed, Aug 11, 2010 at 5:43 PM, Errol errol.kow...@gmail.com wrote: Being a newbie to this, I wasn't sure if each problem should be treated as something unique, or part of the wider picture. I opted for the former, and more of a ticketing approach. Please accept my humblest apologies for erring on the wrong side. However, that said, the last (unanswered) problem has, in my opinion, little to do with typos, and the source code build, and more likely the compiler I'm using in my Ubuntu Jaunty installation. This one is the show stopper. Anyone got any ideas? - regards, Errol Kowald ^ Engenia Pty Ltd, 2 Clear St., Palmerston, ACT 2913, Australia pH:+612 6242 0351 ^ On Wed, 2010-08-11 at 16:00 -0400, John Porubek wrote: (hope no-one is too put-out by my pedantic nit picking) I've got no problems with the nit-picking, but I am a little put off by small changes to each subsequent Subject line so that each message shows up as the start of a new thread (instead of being properly nested as a single thread). Hope no one is too put off by my curmudgeonly response, John -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure
As noted in earlier email to this list, svn for mspgcc4 is left in its legacy state in support of the WASP project. Download either the release tarball of mspgcc4, or clone the git repository. (Sorry if there is still how-to documentation somewhere that implies otherwise. Somebody needs to take charge of new-user step-by-step instructions; my time is overcommitted on getting the two forks back into one. Again this is why I want downstream packaging: so y'all don't *have* to build this stuff yourselves.) The following is more than you need, but should add the packages required for building mspgcc. Peter apt-get install -y \ emacs build-essential checkinstall \ git git-core texinfo \ file patch perl python autoconf automake autotools-dev \ dh-make debhelper devscripts fakeroot gnupg xutils-dev \ lintian pbuilder patchutils \ ncurses-dev libz-dev tk8.4-dev On Thu, Aug 12, 2010 at 3:37 AM, Errol errol.kow...@gmail.com wrote: Thanks for your help Peter. I didn't realise that the root PATH would be different to the user PATH, so after trying to learn how to work around that, I took you advice, at (c), and tried building mspgcc4, from the procedure at http://mspgcc4.sourceforge.net/ What could go wrong? It's only 3 lines. :- ~$ svn checkout https://mspgcc4.svn.sourceforge.net/svnroot/mspgcc4 checked out revision 139 ~$ cd mspgcc4 ~/mspgcc4$ sh buildgcc.sh accepted all of the default choices started the build right now with the result :- Selected GCC 3.2.3 GDB version: 7.0.1 Insight version: 6.8-1 Target location: /opt/msp430-gcc-3.2.3 Binary package name: msp430-gcc-3.2.3_gdb_7.0.1.tar.bz2 - Do you want to start build right now? (y/n) [n] y Running sh do-binutils.sh /opt/msp430-gcc-3.2.3 2.20.1 http://ftp.uni-kl.de; build === makeinfo is missing from path, but required for the binutils build. Please install texinfo. Aborting. === sh do-binutils.sh /opt/msp430-gcc-4.4.3 2.20.1 http://ftp.uni-kl.de; build exited with status code 1. Failed to execute sh do-binutils.sh /opt/msp430-gcc-4.4.3 2.20.1 http://ftp.uni-kl.de; build at ./buildgcc.pl line 247, STDIN line 9. Where is makeinfo? What should PATH= ? What should the root PATH= ? Errol On Wed, 2010-08-11 at 18:08 -0500, Peter Bigot wrote: (a) For a ticketing approach, might be better to create tickets on the sourceforge project instead of emailing everybody with each one. Though I don't know if anybody's going to maintain the how-to for the existing mspgcc infrastructure; my preference is to leave packaging to downstream and just provide the patches. (b) Not sure what the last problem was; the failure to find msp430-ar? Probably you installed binutils in a directory that is not in your PATH. sudo can contribute to confusion there, since the path it uses is not the same as the path you've got in your main shell; contrast msp430-ar -v with sudo msp430-ar -v (c) You might be better off using mspgcc4 until we get the two projects back together. Run the buildgcc.pl script it comes with. Peter On Wed, Aug 11, 2010 at 5:43 PM, Errol errol.kow...@gmail.com wrote: Being a newbie to this, I wasn't sure if each problem should be treated as something unique, or part of the wider picture. I opted for the former, and more of a ticketing approach. Please accept my humblest apologies for erring on the wrong side. However, that said, the last (unanswered) problem has, in my opinion, little to do with typos, and the source code build, and more likely the compiler I'm using in my Ubuntu Jaunty installation. This one is the show stopper. Anyone got any ideas? - regards, Errol Kowald ^ Engenia Pty Ltd, 2 Clear St., Palmerston, ACT 2913, Australia pH:+612 6242 0351 ^ On Wed, 2010-08-11 at 16:00 -0400, John Porubek wrote: (hope no-one is too put-out by my pedantic nit picking) I've got no problems with the nit-picking, but I am a little put off by small changes to each subsequent Subject line so that each message shows up as the start of a new thread (instead of being properly nested as a single thread). Hope no one is too put off by my curmudgeonly response, John -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure
(hope no-one is too put-out by my pedantic nit picking) I've got no problems with the nit-picking, but I am a little put off by small changes to each subsequent Subject line so that each message shows up as the start of a new thread (instead of being properly nested as a single thread). Hope no one is too put off by my curmudgeonly response, John
Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure
Being a newbie to this, I wasn't sure if each problem should be treated as something unique, or part of the wider picture. I opted for the former, and more of a ticketing approach. Please accept my humblest apologies for erring on the wrong side. However, that said, the last (unanswered) problem has, in my opinion, little to do with typos, and the source code build, and more likely the compiler I'm using in my Ubuntu Jaunty installation. This one is the show stopper. Anyone got any ideas? - regards, Errol Kowald ^ Engenia Pty Ltd, 2 Clear St., Palmerston, ACT 2913, Australia pH:+612 6242 0351 ^ On Wed, 2010-08-11 at 16:00 -0400, John Porubek wrote: (hope no-one is too put-out by my pedantic nit picking) I've got no problems with the nit-picking, but I am a little put off by small changes to each subsequent Subject line so that each message shows up as the start of a new thread (instead of being properly nested as a single thread). Hope no one is too put off by my curmudgeonly response, John
[Mspgcc-users] Building MSPGCC from Source Code - The Build procedure
re. https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Building_MSPGCC_from_Source_Code tar --bzip2 -xf binutils-2.19.tar.bz2 mkdir build-binutils cd binutils-2.10 patch -p1 ../packaging/patches/binutils-2.19.patch the last line fails, since the file is actually binutils-2.19-patch a dash has become a dot (hope no-one is too put-out by my pedantic nit picking) - regards, Errol Kowald ^ Engenia Pty Ltd, 2 Clear St., Palmerston, ACT 2913, Australia pH:+612 6242 0351 ^
[Mspgcc-users] Building MSPGCC from Source Code - The Build procedure - su ?
re: https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Building_MSPGCC_from_Source_Code the commands :- cd ../build-binutils ../binutils-2.19/configure --target=msp430 --prefix=/usr/local/msp430 make su make install I don't want to tell people how to suck eggs, I'm possibly nit-picking now, but perhaps a suggestion (for at least the Ubuntu users) sudo make install is safer for the common man? Not only that, but to make su work, I'd have to enable the root user. I don't trust myself enough for that . - regards, Errol Kowald
Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure - su ?
Errol, I'm only programming for the msp under a windows environment, and don't have the time to look into setting up a unix system specifically for the msp here at work. But a tip for Ubuntu: Use the command sudo su to switch user to root which is persistent until you close the terminal or logout of root. Good Luck. Cheers, Ian. Original Message Subject: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure - su ? From: Errol errol.kow...@gmail.com To: source-forge mspgcc mail list mspgcc-users@lists.sourceforge.net Date: 10/08/2010 4:43 PM re: https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Building_MSPGCC_from_Source_Code the commands :- cd ../build-binutils ../binutils-2.19/configure --target=msp430 --prefix=/usr/local/msp430 make su make install I don't want to tell people how to suck eggs, I'm possibly nit-picking now, but perhaps a suggestion (for at least the Ubuntu users) sudo make install is safer for the common man? Not only that, but to make su work, I'd have to enable the root user. I don't trust myself enough for that . - regards, Errol Kowald -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
[Mspgcc-users] Building MSPGCC from Source Code - The build procedure - gcc a grinding halt
re: https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Building_MSPGCC_from_Source_Code the commands :- ~$tar --bzip2 -xf gcc-core-3.2.3.tar.bz2 skipped gcc-g++-3.2.3.tar.bz2 since I don't need c++ ~$cp -av gcc/gcc-3.3/* gcc-3.2.3 ~$mkdir build-gcc ~$cd build-gcc ~/build-gcc$../gcc-3.2.3/configure --target=msp430 --prefix=/usr/local/msp430 ~/build-gcc$make resulted in success ... until msp430-ar resulted in:- *** buffer overflow detected ***: msp430-ar terminated === Backtrace: = /lib/libc.so.6(__fortify_fail+0x37)[0x2aeb64bf0327] /lib/libc.so.6[0x2aeb64bee1d0] /lib/libc.so.6[0x2aeb64bed579] /lib/libc.so.6(_IO_default_xsputn+0x96)[0x2aeb64b67456] /lib/libc.so.6(_IO_padn+0xfa)[0x2aeb64b5ac4a] /lib/libc.so.6(_IO_vfprintf+0x2790)[0x2aeb64b39130] /lib/libc.so.6(__vsprintf_chk+0x99)[0x2aeb64bed619] /lib/libc.so.6(__sprintf_chk+0x80)[0x2aeb64bed560] msp430-ar[0x4095a4] msp430-ar[0x407976] msp430-ar[0x40a0cc] msp430-ar[0x40d3af] msp430-ar[0x40450d] msp430-ar[0x4049d6] msp430-ar[0x40503b] /lib/libc.so.6(__libc_start_main+0xe6)[0x2aeb64b0f5a6] msp430-ar[0x401ec9] === Memory map: 0040-00452000 r-xp 08:01 8036373 /usr/local/msp430/bin/msp430-ar 00651000-00652000 r--p 00051000 08:01 8036373 /usr/local/msp430/bin/msp430-ar 00652000-00653000 rw-p 00052000 08:01 8036373 /usr/local/msp430/bin/msp430-ar 00653000-00655000 rw-p 00653000 00:00 0 01198000-015ad000 rw-p 01198000 00:00 0 [heap] 2aeb648d-2aeb648f r-xp 08:01 9150483 /lib/ld-2.9.so 2aeb648f-2aeb648f3000 rw-p 2aeb648f 00:00 0 2aeb648f3000-2aeb648f4000 r--p 08:01 6815772 /usr/lib/locale/en_AU.utf8/LC_MESSAGES/SYS_LC_MESSAGES 2aeb648f4000-2aeb648fb000 r--s 08:01 4464722 /usr/lib/gconv/gconv-modules.cache 2aeb648fb000-2aeb6493a000 r--p 08:01 6808447 /usr/lib/locale/en_AU.utf8/LC_CTYPE 2aeb6493a000-2aeb64944000 rw-p 2aeb6493a000 00:00 0 2aeb64aef000-2aeb64af r--p 0001f000 08:01 9150483 /lib/ld-2.9.so 2aeb64af-2aeb64af1000 rw-p 0002 08:01 9150483 /lib/ld-2.9.so 2aeb64af1000-2aeb64c59000 r-xp 08:01 9152714 /lib/libc-2.9.so 2aeb64c59000-2aeb64e59000 ---p 00168000 08:01 9152714 /lib/libc-2.9.so 2aeb64e59000-2aeb64e5d000 r--p 00168000 08:01 9152714 /lib/libc-2.9.so 2aeb64e5d000-2aeb64e5e000 rw-p 0016c000 08:01 9152714 /lib/libc-2.9.so 2aeb64e5e000-2aeb64e64000 rw-p 2aeb64e5e000 00:00 0 2aeb64e64000-2aeb64e7a000 r-xp 08:01 9150525 /lib/libgcc_s.so.1 2aeb64e7a000-2aeb6507a000 ---p 00016000 08:01 9150525 /lib/libgcc_s.so.1 2aeb6507a000-2aeb6507b000 r--p 00016000 08:01 9150525 /lib/libgcc_s.so.1 2aeb6507b000-2aeb6507c000 rw-p 00017000 08:01 9150525 /lib/libgcc_s.so.1 7fffc5ee2000-7fffc5ef8000 rw-p 7ffe9000 00:00 0 [stack] 7fffc5fc6000-7fffc5fc7000 r-xp 7fffc5fc6000 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] make[2]: *** [libgcc.a] Aborted make[2]: *** Deleting file `libgcc.a' make[2]: Leaving directory `/home/errol/build-gcc/gcc' make[1]: *** [stmp-multilib] Error 2 make[1]: Leaving directory `/home/errol/build-gcc/gcc' make: *** [all-gcc] Error 2 What would cause a buffer overflow ? If it's any help, I'm running 64 bit Ubuntu Jaunty. er...@engenia:~$ echo $PATH /usr/local/msp430/bin:/usr/local/msp430:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games - regards, Errol Kowald
[Mspgcc-users] Building MSPGCC from Source Code - The build procedure - gcc a grinding halt
re: https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Building_MSPGCC_from_Source_Code the commands :- ~$tar --bzip2 -xf gcc-core-3.2.3.tar.bz2 skipped gcc-g++-3.2.3.tar.bz2 since I don't need c++ ~$cp -av gcc/gcc-3.3/* gcc-3.2.3 ~$mkdir build-gcc ~$cd build-gcc ~/build-gcc$../gcc-3.2.3/configure --target=msp430 --prefix=/usr/local/msp430 ~/build-gcc$make resulted in success ... until msp430-ar resulted in:- *** buffer overflow detected ***: msp430-ar terminated === Backtrace: = /lib/libc.so.6(__fortify_fail+0x37)[0x2aeb64bf0327] /lib/libc.so.6[0x2aeb64bee1d0] /lib/libc.so.6[0x2aeb64bed579] /lib/libc.so.6(_IO_default_xsputn+0x96)[0x2aeb64b67456] /lib/libc.so.6(_IO_padn+0xfa)[0x2aeb64b5ac4a] /lib/libc.so.6(_IO_vfprintf+0x2790)[0x2aeb64b39130] /lib/libc.so.6(__vsprintf_chk+0x99)[0x2aeb64bed619] /lib/libc.so.6(__sprintf_chk+0x80)[0x2aeb64bed560] msp430-ar[0x4095a4] msp430-ar[0x407976] msp430-ar[0x40a0cc] msp430-ar[0x40d3af] msp430-ar[0x40450d] msp430-ar[0x4049d6] msp430-ar[0x40503b] /lib/libc.so.6(__libc_start_main+0xe6)[0x2aeb64b0f5a6] msp430-ar[0x401ec9] === Memory map: 0040-00452000 r-xp 08:01 8036373 /usr/local/msp430/bin/msp430-ar 00651000-00652000 r--p 00051000 08:01 8036373 /usr/local/msp430/bin/msp430-ar 00652000-00653000 rw-p 00052000 08:01 8036373 /usr/local/msp430/bin/msp430-ar 00653000-00655000 rw-p 00653000 00:00 0 01198000-015ad000 rw-p 01198000 00:00 0 [heap] 2aeb648d-2aeb648f r-xp 08:01 9150483 /lib/ld-2.9.so 2aeb648f-2aeb648f3000 rw-p 2aeb648f 00:00 0 2aeb648f3000-2aeb648f4000 r--p 08:01 6815772 /usr/lib/locale/en_AU.utf8/LC_MESSAGES/SYS_LC_MESSAGES 2aeb648f4000-2aeb648fb000 r--s 08:01 4464722 /usr/lib/gconv/gconv-modules.cache 2aeb648fb000-2aeb6493a000 r--p 08:01 6808447 /usr/lib/locale/en_AU.utf8/LC_CTYPE 2aeb6493a000-2aeb64944000 rw-p 2aeb6493a000 00:00 0 2aeb64aef000-2aeb64af r--p 0001f000 08:01 9150483 /lib/ld-2.9.so 2aeb64af-2aeb64af1000 rw-p 0002 08:01 9150483 /lib/ld-2.9.so 2aeb64af1000-2aeb64c59000 r-xp 08:01 9152714 /lib/libc-2.9.so 2aeb64c59000-2aeb64e59000 ---p 00168000 08:01 9152714 /lib/libc-2.9.so 2aeb64e59000-2aeb64e5d000 r--p 00168000 08:01 9152714 /lib/libc-2.9.so 2aeb64e5d000-2aeb64e5e000 rw-p 0016c000 08:01 9152714 /lib/libc-2.9.so 2aeb64e5e000-2aeb64e64000 rw-p 2aeb64e5e000 00:00 0 2aeb64e64000-2aeb64e7a000 r-xp 08:01 9150525 /lib/libgcc_s.so.1 2aeb64e7a000-2aeb6507a000 ---p 00016000 08:01 9150525 /lib/libgcc_s.so.1 2aeb6507a000-2aeb6507b000 r--p 00016000 08:01 9150525 /lib/libgcc_s.so.1 2aeb6507b000-2aeb6507c000 rw-p 00017000 08:01 9150525 /lib/libgcc_s.so.1 7fffc5ee2000-7fffc5ef8000 rw-p 7ffe9000 00:00 0 [stack] 7fffc5fc6000-7fffc5fc7000 r-xp 7fffc5fc6000 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] make[2]: *** [libgcc.a] Aborted make[2]: *** Deleting file `libgcc.a' make[2]: Leaving directory `/home/errol/build-gcc/gcc' make[1]: *** [stmp-multilib] Error 2 make[1]: Leaving directory `/home/errol/build-gcc/gcc' make: *** [all-gcc] Error 2 What would cause a buffer overflow ? If it's any help, I'm running 64 bit Ubuntu Jaunty. er...@engenia:~$ echo $PATH /usr/local/msp430/bin:/usr/local/msp430:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games - regards, Errol Kowald The plot thickens ... ~/build-gcc$make results in no buffer overflow (yet), but, after a fair amount of output, it seems to exit early ... if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi rm -rf ./libgcc.a msp430-ar rc ./libgcc.a libgcc/./_cmpdi2.o libgcc/./_cmpsf2.o libgcc/./__stop_progExec__.o libgcc/./_mulqi3.o libgcc/./_mulhi3.o libgcc/./_mulsi3.o libgcc/./_mulsi3hw.o libgcc/./_umulqihi3.o libgcc/./_mulqihi3.o libgcc/./_udivmodqi4.o libgcc/./_divmodqi4.o libgcc/./_udivmodhi4.o libgcc/./_divmodhi4.o libgcc/./_udivmodsi4.o libgcc/./_divmodsi4.o libgcc/./__prologue_saver.o libgcc/./__epilogue_restorer.o libgcc/./__epilogue_restorer_intr.o libgcc/./_clobbers.o libgcc/./_udivmoddi3_parts.o libgcc/./_udivdi3.o libgcc/./_umoddi3.o libgcc/./_divdi3.o libgcc/./_moddi3.o libgcc/./_muldi3.o libgcc/./_muldi3hw.o libgcc/./_negdi2.o libgcc/./_lshrdi3.o libgcc/./_ashldi3.o libgcc/./_ashrdi3.o libgcc/./_ffsdi2.o libgcc/./_clz.o libgcc/./_ucmpdi2.o libgcc/./_floatdidf.o
Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure - su ?
On Tue, 2010-08-10 at 17:10 +1000, Ian Tait wrote: Use the command sudo su to switch user to root which is persistent until you close the terminal or logout of root. Or just `sudo -i`. R
Re: [Mspgcc-users] Building MSPGCC from Source Code - The Build procedure - su ?
But does it HAVE to be persistent for the build to be successful? Is it not just good enough to switch to root for the install ? When files are being placed in the areas owned by root. - regards, Errol Kowald On Tue, 2010-08-10 at 11:49 +0100, Robert Spanton wrote: On Tue, 2010-08-10 at 17:10 +1000, Ian Tait wrote: Use the command sudo su to switch user to root which is persistent until you close the terminal or logout of root. Or just `sudo -i`. R -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] 'Building MSPGCC from Source Code' - The Build procedure - su ?
But does it HAVE to be persistent for the build to be successful? No, just for the installation. Building as root is invariably a bad idea. However, some distributions do not include sudo by default, and the user doing the building might not be in the sudoers list. I would venture to say that, for the majority of Linux users, the su route is the more effective. But Ubuntu users should probably use sudo. Vic.
