RTEMS web server linking error !

[Nick.SIMON at syntegra.bt.co.uk]

Aha!  My tarfile.o had _binary_o-optimize-tarfile_start etc. in it.  Now
fixed.  Here's a diff on netdemos-4.5.0-beta2/http/Makefile:

59c59,61
< 	$(LD) -r -o $(ARCH)/temp.o  $(ARCH)/init.o -b binary $(ARCH)/tarfile
---
> 	cp $(ARCH)/tarfile .
> 	$(OBJCOPY) -I binary -O elf32-powerpc tarfile $(ARCH)/tarfile.o
> 	$(LD) -r -o $(ARCH)/temp.o  $(ARCH)/init.o $(ARCH)/tarfile.o


I'm not wild about this (esp having elf32-powerpc embedded in it), but it
seems to work.

Thanks for your help,

-- Nick Simon 

> -----Original Message-----
> From: Joel Sherrill [mailto:joel.sherrill at OARcorp.com]
> Sent: 23 May 2000 19:54
> To: Nick.SIMON at syntegra.bt.co.uk
> Subject: Re: RTEMS web server linking error !
> 
> 
> Nick.SIMON at syntegra.bt.co.uk wrote:
> > 
> > A few days ago: Joel wrote:
> > 
> > >
> > > + make a tarfile (or any random binary file)
> > > + use objcopy to convert it to a native .o file
> > >   (I think you get the warning here)
> > > + link using that file.
> > >
> > >
> > 
> > Now I've come back to this, & done (essentially):
> > 
> > powerpc-rtems-objcopy -I binary -O elf32-powerpc tarfile tarfile.o
> > 
> > & then linked in the tarfile.o, using ld as an intermediate 
> step.  I'm now
> > getting a fat warning "cannot represent architecture UNKNOWN" at the
> > objcopy, and undefined _binary_tarfile_start and 
> _binary_tarfile_size.
> > 
> > So:
> > 
> > - Is the warning significant?
> > - Where do the start & size values come from?
> 
> No I don't think so.  
> 
> objcopy adds the symbols around the binary image as it
> converts it.
> 
> > TIA
> > 
> > -- Nick Simon
> 
> -- 
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel at OARcorp.com                 On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>    Support Available             (256) 722-9985
>