Re: [avr-libc-dev] crtusb1287.o not found duing linking.

[Andrew Straw]

Eric Weddington wrote:
>  
>
>   
> > -----Original Message-----
> > From: 
> > address@hidden 
> > [mailto:address@hidden
> > org] On Behalf Of Andrew Straw
> > Sent: Wednesday, March 07, 2007 2:16 AM
> > To: address@hidden
> > Subject: [avr-libc-dev] crtusb1287.o not found duing linking.
> >
> > Hi,
> >
> > I've just built binutils (2.17), gcc (4.1.2), and avr-libc (1.4.5 and 
> > today's CVS) for avr using the instructions here: 
> > http://www.nongnu.org/avr-libc/user-manual/install_tools.html 
> > including 
> > the patch 
> > http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/avr-gcc/file
> > s/patch-newdevices
> >
> > Unfortunately, when my project gets to the final link step, I get the 
> > following error:
> >
> > /usr/local/avr/lib/gcc/avr/4.1.2/../../../../avr/bin/ld: 
> > crtusb1287.o:
> > No such file: No such file or directory
> >     
>
> Did you also include the patches needed for Binutils?:
> <http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/avr-binutils/files/>
> There's a "new devices" patch for binutils as well. If you don't include
> that then the assembler won't know the device, therefore the library (and
> startup code) won't be built for that device in avr-libc.
>
> HTH
> Eric Weddington
>
>   
Hmm, it looks to me like binutils 2.17 already knows about this device 
-- binutils-2.17/gas/config/tc-avr.c contains the following:

static struct mcu_type_s mcu_types[] =
{
...
 {"at90usb1287",AVR_ISA_M128,    bfd_mach_avr5},
...
 {NULL, 0, 0}
};

Furthermore, the patch you link doesn't mention my device, so I'm not 
sure how it would help. Additionally, 
/usr/local/avr/avr/lib/avr5/crtusb1287.o was installed by avr-libc, 
indicating that it did get built. Perhaps gcc doesn't look in this 
directory? (The double "avr" looks a little suspicious to me.)

Hmm, upon further investigation, making a simlink to the crtusb1287.o 
file in my working directory appears to pacify gcc, and now I have a 
newly built hex file. So, it seems it's working 99.9%, but there still 
seems to be some path issue lurking.

Andrew