Re: [avr-libc-dev] How attached are people to the implementation of rand()/random()?

[Georg-Johann Lay]

George Spelvin schrieb:
> > Either Debian is running patches atop GNU, or avr-libc test suite has
> > not been adjusted to factor out different gcc versions.
>
> The Debian diffs can be found in the right-hand column of
> https://packages.debian.org/sid/gcc-avr
> specifically
> http://http.debian.net/debian/pool/main/g/gcc-avr/gcc-avr_4.9.2+Atmel3.5.3-1.diff.gz

That comes with external references, e.g. all the XMEGA stuff and many
others like 55-gcc-4.3.0-attiny167.patch etc.

I'd propose you use GCC trunk HEAD and Binutils master; if that and
rerunning bootstrap does not do the trick, you found a bug and I
wonder how the folks are testing avr-libc :-)

> > Presumably, someone adds this option by hand, because if avr-gcc
> > added it the error message would be "ld: cannot find -latmega128".
>
> That is indeed what runtest.sh does.  Here's the result of "bash -x ./runtest.sh 
> -s".
> The actual compiler invocation is the tenth last line.
>
> [...]
> + avr-gcc -Wundef -I. -gdwarf-4 -W -Wall -pipe -Os -isystem ../../include 
> -nostdlib -std=gnu99 -mmcu=atmega128 -o aux.elf time/aux.c 
> ../../avr/lib/avr51/libc.a ../../avr/lib/avr51/libm.a 
> ../../avr/lib/avr51/atmega128/libatmega128.a -lgcc
> avr-gcc: error: ../../avr/lib/avr51/atmega128/libatmega128.a: No such file or 
> directory

Presumably, it goes like follows: avr-libc detects from the version of
avr-gcc that it does not add -latmega128 and hence skips building
libatmega128.a, hence no such .a in the avr-libc build tree.

Johann