User forums > Embedded development
a problem compiling eeprom of avr(atmega16,winavr) program
scarphin:
Well we are all lucky one of us hit that bug. ;) Can someone pls try building on linux and see if 'avr/lib' should be there in the search path or not, possibly a dev pls?
zage2009:
--- Quote from: jens on August 12, 2011, 09:50:33 am ---
--- Quote from: Aelxx on August 12, 2011, 09:45:19 am ---scarphin - Glad you found your problem's solution.
Zage2009 - No. I use WinXP SP3, C::B rev6454 or Later. I keep my old C::B configurations after reinstalling C::B. And also after reinstalling winAvr I always do manual compiler configuration in C::B, cause C::B doesn't autodetect avr-gcc (IMHO), maybe at this step I remove '$winavr/avr/lib' - can't say, cause I don't remember. Guess scarphin is right and it's some C::B's AVR-GCC compiler configuration bug, and I was lucky not to hit it :D
--- End quote ---
Thes settings are made if you use autodetection, otherwise they stay empty.
--- End quote ---
I reinstall the win7 in vmware Workstation and install the WinAVR,CB10.05(rev6283) in Win7.The result is that the option 'winavr/avr/lib' is still in the Linker tab of the Search directions and perhaps there still is the same problem in different operation system.
scarphin:
It's sure CB adds 'avr/lib' folder automatically to the linker search path. The problem is if it should do this or not. Can someone test under linux and see if the problem also exits on linux or not pls? So the devs can remove it in the next nightly if adding 'avr/lib' to the search path generates this linker problem also under linux.
Jenna:
--- Quote from: scarphin on August 12, 2011, 01:45:28 pm ---It's sure CB adds 'avr/lib' folder automatically to the linker search path. The problem is if it should do this or not. Can someone test under linux and see if the problem also exits on linux or not pls? So the devs can remove it in the next nightly if adding 'avr/lib' to the search path generates this linker problem also under linux.
--- End quote ---
There is another thread about a similar problem on linux.
Here is one of my answers:
http://forums.codeblocks.org/index.php/topic,15118.msg101248.html#msg101248
scarphin:
Yes I'm aware of that thread. Correct me if I'm wrong but the situation there is the inclusion of the GCC libs not the avr-gcc specific libs. As from what I understand someone needs to make sure the problem still exists or not if avr-gcc specific linker libs 'avr/lib' not 'usr/lib' is included. Sry for the trouble if these 2 cases are the same or both libs are installed in the same folder under linux. It's been long since I used linux, just trying to help. ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version