As Dennis W. Tokarski wrote: > /usr/lib/gcc/avr/4.3.3/../../../../avr/bin/ld: crtm1280.o: No such file: No > such file or directory > /usr/lib/gcc/avr/4.3.3/../../../../avr/bin/ld: crtm1281.o: No such file: No > such file or directory > /usr/lib/gcc/avr/4.3.3/../../../../avr/bin/ld: crtm128.o: No such file: No > such file or directory > > The files are definitely there, with 644 perms and owned > by root, just like all the others which work.
Add a -v to the compiler options, and it will tell you the exact linker command line it's using. That should indicate where it is searching for these files. > I don't know if this is an avr-gcc/binutils problem or > an avr-libc problem. It's somehow a problem with that particular toolchain build, albeit I don't have the faintest idea /what/ went wrong. Hmm, one idea just comes to mind: the compiler and library disagree about whether these MCU types belong into either of "avr5" or "avr51" categories. IMHO, this can only happen if the library is built using a different compiler than the compiler you've installed. For an up-to-date Linux toolchain with a decent patchlevel, I'd recommend using Bingo600's Linux build script: http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=42631 -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-libc-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
