From: Gustavo Romero <gromero@linux•vnet.ibm.com>
To: linuxppc-dev@lists•ozlabs.org
Subject: Re: Kernel build issues with upstream binutils
Date: Mon, 17 Jul 2017 09:57:09 -0300 [thread overview]
Message-ID: <596CB425.3000103@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161128003505.61590f63@roar.ozlabs.ibm.com>
Hi,
On bissecting kernel on Debian (gcc version 6.3.0 20170516) I've got the same
error on linking kernels <= v4.9 as reported previously in this thread:
ld: arch/powerpc/boot/zImage.pseries: Not enough room for program headers, try linking with -N
ld: final link failed: Bad value
arch/powerpc/boot/Makefile:364: recipe for target 'arch/powerpc/boot/zImage.pseries' failed
make[1]: *** [arch/powerpc/boot/zImage.pseries] Error 1
arch/powerpc/Makefile:278: recipe for target 'zImage' failed
make: *** [zImage] Error 2
Applying the fix proposed by Nicholas resolved the issue.
However that patch is not present - afaics - in > v4.9 (where it builds fine).
Any clue on why that is happening on <= v4.9 but not on kernels above that?
Thank you.
Regards,
Gustavo
next prev parent reply other threads:[~2017-07-17 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 22:04 Kernel build issues with upstream binutils Anton Blanchard
2016-11-27 13:35 ` Nicholas Piggin
2017-07-17 12:57 ` Gustavo Romero [this message]
2017-07-17 13:05 ` Gustavo Romero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=596CB425.3000103@linux.vnet.ibm.com \
--to=gromero@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox