Brian Dean said: > > Maybe I'll do that at some point, but ... honestly, all I did for each > one was to extract the source and then: > > ./configure --prefix=/usr/local/avr --target=avr > make && make install > > For gcc, you need to add --enable-languages=c to the configure. > > Avr-libc was a little picky about the compile directory. For it, do, at > the top level source directory: > > mkdir obj && cd obj && --configure --prefix=/usr/local/avr && make > && make install > > Avarice requires you to tell it explicitly where the bfd lib was > installed since binutils seems to install it in a place where other > tools don't look for it. You also need to have libintl installed and to > tell it where that was if I recall. > This is all that I've done as well, but from recent discussion there is probably a handful of patches that needed to be added before the tools were built... >> hair, I lost a lot of that trying to get the OSX tool chain working >> (despite following ononline guide and buying a bloody keyspan >> USB->Serial convertor which OSX ignores!) > > I use the Keyspan USA-19HS - it has worked fine for me from day one. In > fact, I have 4 of them in use simultaneous for 4 serial ports - one to > the STK500, two to my target board, and one for a second STK500. My Keyspan adapter also works flawlessly. I've also seen mention that if you need more than 1 adapter and you don't want the port names to change in Mac OS X to use their 4 port adapter. I believe there is also one that includes a parallel port, but I'm not sure of what use that would be on a Mac. Mike
Message
Re: [AVR-Chat] OT: monitors (was: Oh, I am so tired of this...)
2005-03-17 by Mike Murphree
Attachments
- No local attachments were found for this message.