Revert "x86: Make relocatable kernel work with new binutils"
This reverts commit 86b1e8dd83cb ("x86: Make relocatable kernel work with
new binutils").
Markus Trippelsdorf reported a boot failure caused by this patch.
It might be that the issue does not occur with the binutils in Oneiric anyway, as the reverted kernel patch (86b1e8dd83cb) mentions a binutils version range with an upper limit. I have not tried building a kernel with CONFIG_RELOCATABLE=y on Oneiric to find out. If binutils behaviour was changed a second time, fixing this issue, it might be more helpful to backport the binutils change to Maverick instead of a kernel change.
Hi Leann,
The patch you said is included upstream was reverted the next day in v2.6.38-rc2, so the reason given for Fix Released status is not applicable.
I don't have permission to revert the status change, so please do that if you agree.
$ git describe --contains 6b35eb9ddcddde7 b510726de03fae0 71178f1ec4
v2.6.38-rc2~32^2~1
commit 6b35eb9ddcddde7 b510726de03fae0 71178f1ec4
Author: Ingo Molnar <email address hidden>
Date: Wed Jan 19 10:09:42 2011 +0100
Revert "x86: Make relocatable kernel work with new binutils"
This reverts commit 86b1e8dd83cb ("x86: Make relocatable kernel work with
new binutils").
Markus Trippelsdorf reported a boot failure caused by this patch.
It might be that the issue does not occur with the binutils in Oneiric anyway, as the reverted kernel patch (86b1e8dd83cb) mentions a binutils version range with an upper limit. I have not tried building a kernel with CONFIG_ RELOCATABLE= y on Oneiric to find out. If binutils behaviour was changed a second time, fixing this issue, it might be more helpful to backport the binutils change to Maverick instead of a kernel change.