Razvan, It works. Thanks a lot! I think someone may update the wiki page to include this method.
On Wed, Jul 15, 2009 at 11:35 AM, Razvan Musaloiu-E. <[email protected]>wrote: > Hi! > > On Wed, 15 Jul 2009, Xin Dong wrote: > > Hi guys, >> I have the same problem on my Mac OS X 10.5 for intel. I used to be able >> to >> compile apps for micaz, but now I don't know why suddenly I can't. I tried >> to install avr-gcc from MacPorts, but still without luck. >> >> Has anyone figured out what's going on here? >> >> > Can you give a try the macports from here: > http://hinrg.cs.jhu.edu/git/?p=ports.git > > -- > Razvan ME > > 2009/6/10 David Gay <[email protected]> >> >> 2009/6/10 André Lopes <[email protected]>: >>> >>>> -And nesc1 gets those paths from the gcc invocation - the two problems >>>> -are undoubtably related. >>>> >>>> How should I add the gcc search path at avr-gcc invocation? >>>> >>> >>> Nothing. Those paths being missing is just a symptom of the same problem. >>> >>> nesc1: internal error: couldn't define builtin macros - exiting >>>>> >>>>> I've runned that command and it printed a lot of #DEFINE values, the >>>>> only >>>>> thing >>>>> that a think it could be wrong is some warnings that it gave me, like, >>>>> >>>>> ignoring nonexistent directory >>>>> >>>>> >>>> "/stow/repository/avr-tinyos/bin/../lib/gcc/avr/4.1.2/../../../../avr/sys-include" >>> >>> ignoring nonexistent directory >>>>> "/opt/local/avr-build/avr-tinyos/lib/gcc/avr/4.1.2/include" >>>>> ignoring nonexistent directory >>>>> "/opt/local/avr-build/avr-tinyos/avr/sys-include" ignoring nonexistent >>>>> directory >>>>> >>>> "/opt/local/avr-build/avr-tinyos/avr/include" >>>> >>>>> >>>>> I've tried to reinstall avr tools avr-gcc, but always the same error, >>>>> getting desperate! >>>>> >>>> >>>> -What's the result code from avr-gcc? (run echo $? *immediately* after >>>> -the manual call to avr-gcc to find out) nesc1 won't be happy if it's >>>> -not 0. >>>> >>>> >>>> >>>> The value printed is 1. >>>> >>> >>> That's your problem - nesc expects a result of 0 (indicating success). >>> Maybe it should be a little more lenient when the result is 1 >>> (typically means "warning") - I'll probably change that for the next >>> release. >>> >>> How should I proceed? Thanks in advance for the time helping me! >>>> >>> >>> Install an avr-gcc that doesn't have installation problems (the >>> presence of those /stow paths in the messages from avr-gcc suggests to >>> me that you've got something broken in your build process) ? FWIW, I >>> haven't had any problems with the avr-gcc (4.0.2) that comes with >>> DarwinPorts (http://darwinports.com) >>> >>> David Gay >>> >>> _______________________________________________ >>> Tinyos-help mailing list >>> [email protected] >>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >>>
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
