(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
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
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
(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
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
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
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
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 :-
~$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/*
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/*
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
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
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,
13 matches
Mail list logo
