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

[Georg-Johann Lay]

George Spelvin schrieb:
> Thanks for the help.  It's not on the critical path yet, but I would
> like to get some self-tests working.
>
> > This looks strange. With avr-libc from trunk and a reasonable
> > up to date avr-gcc (5.2+) the crt should be located in
> >
> > $prefix/avr/lib/avr51/crtatmega128.o
>
> Perhaps the fact (I mentioned in in passing in a previous message to
> the list) that I'm using 4.9.2 (because that's what Debian has packaged)
> has had an effect?

avr-gcc 4.9 shouldn't try to link against libatmega128.a at all, and
this is how my 4.9.2-pre1 (home-brew canadian cross) behaves.
avr-gcc 4.9 defines a spec function to add -lm128, but that spec
function is dead :-)

http://gcc.gnu.org/viewcvs/gcc/branches/gcc-4_9-branch/gcc/config/avr/avr.h?view=markup#l495

The question is where the libatmega128.a is coming fromcomes from...
Either Debian is running patches atop GNU, or avr-libc test suite has
not been adjusted to factor out different gcc versions.

Presumably, someone adds this option by hand, because if avr-gcc
added it the error message would be "ld: cannot find -latmega128".

> Another thing is that I haven't installed *anything* yet; there is no
> $prefix/avr directory.  I was assuming that the tests would run against
> the built tree *before* installation.  (If I can't run "make check"
> before "make install", that smells like a bug that needs fixing.)

Well, I never ran avr-libc tests, I am just doing the avr-gcc thing...

Maybe for the time being it's the simplest approach to build your own
GCC and Binutils all with same $prefix in $HOME, dito for libc.

avr-libc can build against non-installed avr-gcc by
CC="$build/gcc/xgcc -B$build/gcc" where $build refers to the gcc
build dir, which should never be in $source b.t.w.

Johann