Subject: Re: link_set_... sections and objcopy
To: Richard Earnshaw <Richard.Earnshaw@arm.com>
From: Jason Thorpe <email@example.com>
Date: 04/27/2004 13:42:26
Content-Type: text/plain; charset=US-ASCII; format=flowed
On Apr 27, 2004, at 11:28 AM, Richard Earnshaw wrote:
> Yet again I've been bitten by the objcopy bug that causes the a.out
> version of the kernel image to have the .data and .bss sections at the
> wrong vma.
Ack. I thought I fixed that in the a.out back-end a while ago.
> Can you think of any reason (other than the fact that it make the
> more complex) why we can't just work around the problem by using the
> following in link scripts for affected platforms?
Yes. Because explicitly listing the link sets in the linker script
defeats the purpose of them. Any arbitrary code can define additional
link sets, which would then have to be listed here in the linker
We really need to figure out how to make the a.out back-end copy them
-- Jason R. Thorpe <firstname.lastname@example.org>
content-type: application/pgp-signature; x-mac-type=70674453;
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
-----END PGP SIGNATURE-----