Re: Link Error: Relocation overflow for relocation entry
Re: Link Error: Relocation overflow for relocation entry
- Subject: Re: Link Error: Relocation overflow for relocation entry
- From: Bob Clark <email@hidden>
- Date: Thu, 22 Sep 2005 21:18:27 -0700
I am seeing one of my object files with a data section total of 70998
(kilobytes = 70Mb?) and a text section of 444606 (444Mb??).
Is this the right way to look at it?
Do these sections have to be smaller than 32Mb? Both?
I think that's correct.
I have about 12 object files that have a greater size than 30000 data
section.
I have about 52 object files that have a greater size than 30000 text
section.
Could this be the problem? Perhaps I can break these files up...or
recruit some other programmers to help with this stage of converting
from CodeWarrior to Xcode.
Thanks for any advice you can give me, I would like to avoid spending
the DTS incident. I will if necessary.
I think you mentioned that you have a bunch of really big arrays. A
brain-dead way to get past the linker might be to allocate those arrays
(in the heap) at runtime. If you got really cutesy I suppose you could
even set up C++ objects whose constructors allocated the arrays.
But if you replaced global variables like
char gBigArray[1024*1024];
with stuff like
char* gBigArray = NULL;
then in the code do
gBigArray = new char[1024*1024];
you'd have your big array and it would live happily in the heap without
obstructing the link.
(This is mostly speculation though, since my problem ended up not
really being because of humongous text sections.)
--Bob
--
Bob Clark
Clarkwood Software, LLC
http://www.clarkwood.com/
Mac OS X Software
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden