Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1743330 > unrolled thread
| Started by | Bob Tracy <rct@gherkin.frus.com> |
|---|---|
| First post | 2018-10-24 16:50 +0200 |
| Last post | 2018-10-25 04:40 +0200 |
| Articles | 2 — 1 participant |
Back to article view | Back to linux.kernel
vmlinux ld relocation errors on Alpha Bob Tracy <rct@gherkin.frus.com> - 2018-10-24 16:50 +0200
Re: vmlinux ld relocation errors on Alpha Bob Tracy <rct@gherkin.frus.com> - 2018-10-25 04:40 +0200
| From | Bob Tracy <rct@gherkin.frus.com> |
|---|---|
| Date | 2018-10-24 16:50 +0200 |
| Subject | vmlinux ld relocation errors on Alpha |
| Message-ID | <wMsDU-3s8-7@gated-at.bofh.it> |
Back in January of 2017, a patch set was created for the 4.9.0 kernel and *hopefully* sent upstream to address the subject issue. The patch implemented a workaround: defining a new "alphalib" section for all the Alpha-specific library functions to be linked into the final vmlinux. The patch was definitely not implemented in a vacuum: Helge Deller and Michael Cree suggested the fix approach, and both Maciej W. Rozycki and Matt Turner provided significant input along the way. At this late date, I was forced to resync my Alpha build tree with the one from "kernel.org", and noticed the patch set never made it into mainline. There's a definite possibility it was never submitted upstream, and a further possibility it was NACK'd for some reason. Am currently attempting a native 4.19.0 build with an up-to-date debian "sid" toolchain. If the build succeeds, than the issue became OBE for whatever reason. Otherwise, it would be nice to know what happened to the patch set. Should know either way as far as the build in a few more hours. --Bob
[toc] | [next] | [standalone]
| From | Bob Tracy <rct@gherkin.frus.com> |
|---|---|
| Date | 2018-10-25 04:40 +0200 |
| Message-ID | <wMDIZ-1Id-3@gated-at.bofh.it> |
| In reply to | #1743330 |
On Wed, Oct 24, 2018 at 09:46:29AM -0500, Bob Tracy wrote: > Back in January of 2017, a patch set was created for the 4.9.0 kernel and > *hopefully* sent upstream to address the subject issue. > (...). > Am currently attempting a native 4.19.0 build with an up-to-date debian > "sid" toolchain. If the build succeeds, than the issue became OBE for > whatever reason. Otherwise, it would be nice to know what happened to > the patch set. Should know either way as far as the build in a few more > hours. Successful build, so I guess "OBE" applies. If someone reading this knows, how was this fixed? My guess would be improvements in the compiler tool chain, most particularly "bintools". Sorry for the noise. --Bob
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web