This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Gcc driver and -T option
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: 7400 <U7400 at netscape dot net>
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 29 Aug 2002 08:57:08 -0400
- Subject: Re: Gcc driver and -T option
- References: <599D0F59.74F35C06.0000F094@netscape.net>
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