This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.

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

Re: ld needing libgcc

To: Philip Blundell <pb@nexus.co.uk>
Subject: Re: ld needing libgcc
From: Mark Pulver <mpulver@research.canon.com.au>
Date: Wed, 25 Aug 1999 10:56:56 +1000 (EST)
Cc: Mark Pulver <mpulver@research.canon.com.au>,crossgcc@sourceware.cygnus.com
References: <14272.32157.773407.416095@hodges.research.canon.com.au><E11IrRS-0006c5-00@fountain.nexus.co.uk>

Philip Blundell writes:
 > You should never call ld directly.  If libc is generating errors then it 
 > sounds like newlib needs fixing.  The lack of __end__ might be an oversight in 
 > the linker script.

What should __end__ be assigned to (end of what?, data, text, bss)?

Also which is the ldscripts that is used (or when is it called):
% ls ldscripts/
armelf.x        armelf.xn       armelf.xs
armelf.xbn      armelf.xr       armelf.xu


Thanks,
	Mark

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

Follow-Ups:
- Re: ld needing libgcc
  - From: Philip Blundell <pb@nexus.co.uk>

References:
- Re: ld needing libgcc
  - From: Mark Pulver <mpulver@research.canon.com.au>
- Re: ld needing libgcc
  - From: Philip Blundell <pb@nexus.co.uk>

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