Brian, > 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 huh? > For gcc, you need to add --enable-languages=c to the configure. ok, perhaps I shoudl explain, I know nothing about unix :-) I can do LS, and I know about changing owners and permissions, but thats where it ends. > If the primary issue is an unfamiliarity with Unix development, most > any good Unix book will apply directly to MacOS X for the most part. thats the big issue :-) I hate to say it, but on windows, all I do is hit 'install' and it works :-) > While Eagle runs very well on MacOS X, I admit it definitely requires > some getting used to. I've learned to work with it, it does what I > need, but there is a learning curve. But that is not specific to the > MacOS X port - I've heard the same complaint from Windows users. yeah, the trouble is the only time I need to use it, I need something quick'ish.. > I use the Keyspan USA-19HS - it has worked fine for me from day one. doesn't for me, OSX doesn't see it at all, at least I can see any serial devices appear anywhere (/etc/dev/ I think is where itshould appear). Paul
Message
Re: [AVR-Chat] OT: monitors (was: Oh, I am so tired of this...)
2005-03-18 by Paul Maddox
Attachments
- No local attachments were found for this message.