On Sun, Nov 20, 2011 at 11:11 AM, Andy Warner <an...@pobox.com> wrote:
> The problem was that msp430-gcc doesn't try and run "msp430-as", it tries
> to find "as", and looks in some specific places. Strace shows that it is
> looking in:
>
> /usr/local/lib/gcc/msp430/4.5.3/../../../../msp430/bin/
I noticed your first message suggested you were configuring gcc with:
--program-prefix=msp430-
which is not one of the recommended flags in the gcc patch for msp430
support. I don't know why that would have something to do with it,
except that the problem seems to involve the wrong guess for a program
prefix.
If the process you used to build binutils and gcc isn't consistent
with the process described at the top of the toolchain patches
(specifically in terms of configuration options and the need to build
outside the source tree), something there might be the basis of the
problem. With normal configuration, none of the cross-compiler tools
should be installed in ${bindir} without a target prefix; they're only
installed that way inside
${prefix}/${target}/bin---/usr/local/msp430/bin, in your case---which
is not normally in the path.
Peter
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
