On 02/08/17 13:30, Erik Christiansen wrote:
That's not looking good at all. Now we have two simple generic compiler
tests that avr-gcc is failing for the atmega1284p. To confirm that it is
avr-gcc asking for a non-existent crt file, and not a path issue, I'd
try the following, which on my older version gives:
$ locate crtm1284 crtatmega1284
/usr/lib/avr/lib/avr5/crtm1284p.o
/usr/lib/avr/lib/avr51/crtm1284p.o
locate crtm1284 crtatmega1284
/opt/avr-libc2.0.0-binutils2.9/avr/lib/avr51/crtm1284.o
/opt/avr-libc2.0.0-binutils2.9/avr/lib/avr51/crtm1284p.o
/opt/avr-libc2.0.0-binutils2.9/avr/lib/avr51/crtm1284rfr2.o
/opt/avr8-gnu-toolchain-linux_x86_64/avr/lib/avr51/crtatmega1284.o
/opt/avr8-gnu-toolchain-linux_x86_64/avr/lib/avr51/crtatmega1284p.o
/opt/avr8-gnu-toolchain-linux_x86_64/avr/lib/avr51/crtatmega1284rfr2.o
Where
/opt/avr8-gnu-toolchain-linux_x86_64/... is my existing (working) toolchain
/opt/avr-libc2.0.0-binutils2.9/... is the new (borked?) toolchain
So, it looks like it won't find these files. I'm curious that your
'locate' above found the same names as this new version and that my
'working' version does not have the same filenames.
Hmmm.. food for thought.
Please mail me off-list if you would like to (I think you have my e-mail).
Cheers
Bob
--
The Sun is out, the sky is blue, it's time to drive the MR2.
_______________________________________________
AVR-chat mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/avr-chat