summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended
diff options
context:
space:
mode:
authorLaurentiu Palcu <laurentiu.palcu@intel.com>2012-11-21 16:57:42 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-11-24 15:12:29 +0000
commitf862f06f32d1e95c8071d4845684c77cf124ab55 (patch)
tree80cb1b58c26a206d32bef52758923fa05b089ed7 /meta/recipes-extended
parente2143b373983fd3e85d78dc9b34cd386ceccc285 (diff)
downloadast2050-yocto-poky-f862f06f32d1e95c8071d4845684c77cf124ab55.zip
ast2050-yocto-poky-f862f06f32d1e95c8071d4845684c77cf124ab55.tar.gz
binutils-crosssdk: do not set .interp size to 0x1000 for partial linked objects
When building the SDK, the final .interp section size should be set to a bigger value (0x1000) in order to be able to change the dynamic loader's path later. However, we shouldn't do that for partial linked objects (when -r or -rU is used). That's because those objects will then have an .interp section of 0x1000 even if it contains no data and when the final linking is done we will end up with a "cannot move location counter backwards" error. That's because the linker will try to squeeze all the data in the .interp sections found in various partial linked objects into one 0x1000 bytes final .interp section. [YOCTO #3264] (From OE-Core rev: b25d0c5fe286e44ded46aefdcbe35ed259087759) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud