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 <[email protected]> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
>
>
