Well, you've made it one level deeper into the beast, but it looks like
perhaps you don't have the ATMEGA gcc compiler. Mine's in:
enfield:schip [390] type avr-gcc
avr-gcc is /usr/avr/tbin/avr-gcc
or perhaps you don't have that directory in your PATH.
whee, isn't this fun?
MS
Ellen Shlossberg wrote:
> Hi Michael,
>
> Thanks for the suggestion. I've decided to try the complete install
> TinyOS 2.1.0 from Ubuntu's synaptic package instead (as described here):
>
> http://mythicalcomputer.blogspot.com/2008/08/installation-of-tinyos-in-ubuntu.html
>
> It was very simple to install, and I did not have to compile nesC. The
> previous error has gone away and I have a version of ncc:
>
> $ ncc --version
> ncc: 1.2.4
> nescc: 1.3.0
> gcc: gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> $ which ncc
> /usr/bin/ncc
> $ which nescc
> /usr/local/msp430/bin/nescc
>
> Now, when I try to install Blink, I get a different error:
>
> $ make mica2
> mkdir -p build/mica2
> compiling BlinkAppC to a mica2 binary
> ncc -o build/mica2/main.exe -Os -Wall -Wshadow -Wnesc-all -target=mica2
> -fnesc-cfile=build/mica2/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22
> -finline-limit=100000 -DIDENT_APPNAME=\"BlinkAppC\"
> -DIDENT_USERNAME=\"aimee\" -DIDENT_HOSTNAME=\"desktop-zussman\"
> -DIDENT_USERHASH=0x34a40d82L -DIDENT_TIMESTAMP=0x4a662f2aL
> -DIDENT_UIDHASH=0xb1fa3874L -fnesc-dump=wiring
> -fnesc-dump='interfaces(!abstract())'
> -fnesc-dump='referenced(interfacedefs, components)'
> -fnesc-dumpfile=build/mica2/wiring-check.xml BlinkAppC.nc -lm
> Couldn't execute avr-gcc
> make: *** [exe0] Error 2
>
> I've seen suggestions on changing mig parameters to show:
> % mig target=Mica2
>
> But that hasn't helped. Any other suggestions on what the "Couldn't
> execute avr-gcc" error could mean?
>
> Thanks,
> Ellen
>
>
> On Tue, Jul 21, 2009 at 5:01 PM, Michael Schippling <[email protected]
> <mailto:[email protected]>> wrote:
>
> I have both ncc and tos-yadayada in /usr/bin
> Unfortunately I have no idea what part of the TOS install
> provides them. However your checkout is only getting the
> source code, not the tools. See if you can find instructions
> for a full TOS install on your dev platform and intuit
> the pieces you have missed.
>
> MS
>
> Ellen Shlossberg wrote:
>
> Hello All,
>
> I am installing TinyOS 2.x on a Windows machine running Ubuntu.
> I got the directories through CVS here:
>
> |cvs
> -d:pserver:[email protected]:/cvsroot/tinyos
> login
> cvs -z3
> -d:pserver:[email protected]:/cvsroot/tinyos
> co tinyos-2.x
>
> cvs -z3
> -d:pserver:[email protected]:/cvsroot/tinyos
> co tinyos-2.x-contrib|
>
> And installed the NesC compiler, so that it shows:
>
> $ nescc --version
> nescc: 1.3.1
> gcc: gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
>
> However, it looks like I do not have ncc, which is strange
> because I assumed it would come with the TinyOS installation
> files. Here is the error I get when I try to install the Blink
> program:
>
> $ sudo make mica2
> /bin/sh: tos-ident-flags: command not found
> mkdir -p build/mica2
> compiling BlinkAppC to a mica2 binary
> ncc -o build/mica2/main.exe -Os -fnesc-separator=__ -Wall
> -Wshadow -Wnesc-all -target=mica2 -fnesc-cfile=build/mica2/app.c
> -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 -finline-limit=100000
> -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())'
> -fnesc-dump='referenced(interfacedefs, components)'
> -fnesc-dumpfile=build/mica2/wiring-check.xml BlinkAppC.nc -lm
> make: ncc: Command not found
> make: *** [exe0] Error 127
> ai...@desktop-zussman-1:/opt/tinyos-2.x/apps/Blink$
>
> Does anyone know how to address the missing ncc executable
> issue, and while the tos-ident-flags is not in my TinyOS
> installation? Or maybe suggest another reason why this program
> isn't compiling?
>
> Many thanks,
> Ellen
>
> --
> Ellen Shlossberg
> Columbia University
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> <mailto:[email protected]>
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
>
> --
> Ellen Shlossberg
> Columbia University
> MS Electrical Engineering
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
