Gcc driver and -T option

Daniel Jacobowitz drow@mvista.com
Thu Aug 29 05:56:00 GMT 2002


On Thu, Aug 29, 2002 at 08:17:23AM -0400, 7400 wrote:
> Thanks for replying.  Here is some relevant  part from the linker script that is linked explicitly.
> Basically I'm creating the overlay of data and rodata from 1.o and 2.o 
> If I don't include 1.o 2.o , how should I achieve this overlay ?
> Any idea ?
> 
>  OVERLAY :
>   {
>     .program0_pd_data
>     { 
>         __program0_data_start = .;
>        1.o (.data)
>        1.o (.rodata)
>        . = ALIGN(32 / 8);
>         __program0_bss_start = .;
>        1.o (.bss)
>        . = ALIGN(32 / 8);
>         __program0_bss_end = .;
>     }
>     .program1_pd_data
>     { 
>         __program1_data_start = .;
>        2.o (.data)
>        2.o (.rodata)
>        . = ALIGN(32 / 8);
>         __program1_bss_start = .;
>        2.o (.bss)
>        . = ALIGN(32 / 8);
>         __program1_bss_end = .;
>     }
>   }
> There could be other situations where one needs to specify the object files in the linker script. If that is the case , then shouldn't driver detect 
> explict usage of linker script and hence generate .o s in the current directory ?

That's a bit out of GCC's realm.  You should really just compile the
objects yourself with -c.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer



More information about the Gcc-bugs mailing list