Your message dated Sat, 19 Dec 2015 11:16:04 +0300
with message-id <20151219081604.gq3...@home.paul.comp>
and subject line Re: Bug#808114: avr-libc in Debian testing is incompatible
with gcc-avr, linking fails
has caused the Debian Bug report #808114,
regarding avr-libc in Debian testing is incompatible with gcc-avr, linking fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
808114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: avr-libc
Version: 1:1.8.0+Atmel3.4.5-1
Severity: grave
This current version depends on gcc-avr (>= 1:4.8.1+Atmel3.4.5), and
testing already ships 1:4.9.2+Atmel3.5.0-1 which formally fulfills the
dependency, however, the resulting combination is unusable as the
specs files supplied with gcc-avr 1:4.9.2+Atmel3.5.0-1 list startup
files like "crtatmega128.o", and this specific avr-libc version
provides "crtm128.o". There's also no device-specific lib present so
upon linking an example demo project these errors are produced:
$ make
avr-gcc -g -Wall -O2 -mmcu=atmega8 -c -o demo.o demo.c
avr-gcc -g -Wall -O2 -mmcu=atmega8 -Wl,-Map,demo.map -o demo.elf demo.o
/usr/lib/gcc/avr/4.9.2/../../../avr/bin/ld: cannot find crtatmega8.o: No such
file or directory
/usr/lib/gcc/avr/4.9.2/../../../avr/bin/ld: cannot find -latmega8
collect2: error: ld returned 1 exit status
Makefile:75: recipe for target 'demo.elf' failed
make: *** [demo.elf] Error 1
Thank you in advance.
--- End Message ---
--- Begin Message ---
Version: 1:1.8.0+Atmel3.5.0-1
I can confirm that gcc-avr and avr-libc are in sync in Debian testing
now, and work as expected.
Thank you!
--- End Message ---
