This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: M68k a.out grief


"Holland, Alexander MHX" wrote:
> 
> In order to use a particular in-circuit emulator, I switched  from a GNU
> 2.95.2 m68k-coff target format to a GNU 2.95.2 m68k-aout format. However, I
> am running into problems creating a linker script that provides even a
> minimum level of output section control. For example, my COFF script creates
> a ".vectors" section, specifies that the data part of my vectors module (a
> vector table data struct) go into this section, and locates the section at
> the base of ROM. The a.out linker seems not to allow me to specify any
> section different from the standard .text, .data, .bss. Does anyone have any
> a.out linker script examples or techniques that provide more flexible output
> section control?

If I recall correctly, a.out format ONLY support the three basic
sections (text, data and bss).  You might look into linking under coff
and using objcopy to covert to an a.out load module.  I've never looked
into how objcopy maps sections.

Art

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]