Re: [avr-chat] New avr-libc

[Bob von Knobloch]

On 01/08/17 11:40, Erik Christiansen wrote:
> Hi Bob,
>
> Have you tried without the "-c", i.e. a single-step compile? If that
> works, then avr-gcc is handing over some needed parameter to avr-ld.

Hi Erik,
Same output without "-c"

> But for diagnosis, what is listed after the linker script when you:
>
> $ avr-gcc -mmcu=atmega1284p -Wl,--verbose | more

attempt to open crtatmega1284p.o failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libgcc.so failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libgcc.a succeeded
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libm.so failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libm.a failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/avr51/libm.so 
failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/avr51/libm.a 
succeeded
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libc.so failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libc.a failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/avr51/libc.so 
failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/avr51/libc.a 
succeeded
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libatmega1284p.so 
failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/avr51/libatmega1284p.a 
failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/avr51/libatmega1284p.so 
failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/avr51/libatmega1284p.a 
failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/libatmega1284p.so failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/libatmega1284p.a failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/libatmega1284p.so 
failed
attempt to open 
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/lib/libatmega1284p.a 
failed
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/bin/ld: 
cannot find crtatmega1284p.o: No such file or directory
/opt/avr-libc2.0.0-binutils2.9/lib64/gcc/avr/5.4.0/../../../../avr/bin/ld: 
cannot find -latmega1284p
collect2: error: ld returned 1 exit status
> If it's not looking where yours are, then I'd first ask whether binutils
> was built before gcc, to make them available.

It was (I built the whole toolchain new - binutils first - no errors 
issued during the build).

> > I notice that, under '/opt/avr-libc2.0.0-binutils2.9/avr/lib/avr51/
> > the 'crt' files appear to have different names (when compared to my existing
> > tool chain):
> > Old = crtatmega1284p.o
> > New = crtm1284p.o
> >
> > Have I missed some parameter that the compilation of the linker needed to be
> > able find these files? Why are they renamed?
>
> Dunno. You're not by any chance invoking the old avr-gcc (with old names
> and library paths)? It is not at all difficult to have the old executable
> not only still lying about, but first in $PATH, if the new is not
> installed over it.

No, totally separate directory trees for the old & new versions.
Just 1 symlink to change from old to new.

Thanks for the advice.
How's it going on the farm down under?

Bob
--
The Sun is out, the sky is blue, it's time to drive the MR2.