mkelfImage problem

[ron minnich]

I've got an elfImage that has a text segment at 800000.

When I run mkelfImage from the latest CVS, the elfImage that is created 
has that chunk at 800000 moved down to 100000. The segment in elfImage at 
100000 has the exact size of the segment at 800000 in the input elf file.

OK, anybody seen anything like this? any hints :-)

ron

ron minnich  writes:
> I've got an elfImage that has a text segment at 800000.

Is this a linux kernel?  If not mkelfImage 1.x does not apply.
> When I run mkelfImage from the latest CVS, the elfImage that is created 
> has that chunk at 800000 moved down to 100000. The segment in elfImage at 
> 100000 has the exact size of the segment at 800000 in the input elf file.
>
> OK, anybody seen anything like this? any hints :-)

Have you tried the latest mkelfImage from my site.

Sorry for being slow in this sync up I have a nasty cold right
now, plus quite a few things are catching up to me that I put
off while writing romcc.

Eric

[ron minnich]

On 11 Apr 2003, Eric W. Biederman wrote:
> ron minnich  writes:
> > I've got an elfImage that has a text segment at 800000.
>
> Is this a linux kernel?  If not mkelfImage 1.x does not apply.

never mind, it was a big mistake on my part.

I was reconstructing last summer's plan9 work and my brain glitched :-)

Sorry if I made your cold worse :-)

ron

ron minnich  writes:
> On 11 Apr 2003, Eric W. Biederman wrote:
> > ron minnich  writes:
> > > I've got an elfImage that has a text segment at 800000.
> >
> > Is this a linux kernel?  If not mkelfImage 1.x does not apply.
>
> never mind, it was a big mistake on my part.
>
> I was reconstructing last summer's plan9 work and my brain glitched :-)

Ah.  If you can send me a patch for mkelfImage-2.3 I would appreciate
it. -t plan9 sounds nice.
> Sorry if I made your cold worse :-)

No problem I just figured an explanation was useful.

Eric