Re: startup embedded target

["William A. Gatliff" <bgat at saturn dot billgatliff dot com>]

Jan:


If you make a cross-reference file (an option to the linker), then it
will tell you why the 'startup' label exists.

I think that in addition to --nostartfiles, you also want --nodefaultlibs.

b.g.

On Tue, Jul 24, 2001 at 04:17:26PM +0200, Vermeulen Jan wrote:
> 
> >Try the following :
> >
> > SECTIONS {
> >   .vector0 :
> >    {
> >     LONG( __stack )
> >    } > rom1
> >   .vector1 :
> >    {
> >     LONG( ABSOLUTE( main ) ) /* or _main depending on the compiler */
> >    } > rom1
> >.....
> >
> >Since these are the 2 first sections that go into rom1, the value for stack
> >will be int the 4 first bytes and the value for main will be int the 4 next
> >ones.
> >
> >Giovanni Caterina
> 
> Thanks for the wonderful suggestions, but unfortunatly it does not work. :'(
> At 0x0 is the code with label 'startup'. Probably something that is in the
> startupcode.
> (I assume that it is in crt.0)
> 
> I tried with "-nostartfiles" but it is the same thing. At 0x0, there is code
> for some kind of routine that is not in my "main.c" file (only main and
> WritePortB to write the LED code).
> 
> I only want my m68k-coff-gcc to compile those 2 routines : main() and
> WritePortB(unsigned char c) and nothing else. 
> 
> How can I find the error I made and how do I proceed ?
> Thanks,
> Jan
> 
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
> 

-- 
Bill Gatliff
bgat@billgatliff.com

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