Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
You need to sign in or sign up before continuing.
  • linux
  • scripts
  • Kconfig.include
Find file BlameHistoryPermalink
  • Thomas Gleixner's avatar
    kbuild: Fail if gold linker is detected · 75959d44
    Thomas Gleixner authored Jul 16, 2019
    
    
    The gold linker has known issues of failing the build both in random and in
    predictible ways:
    
     - The x86/X32 VDSO build fails with:
    
       arch/x86/entry/vdso/vclock_gettime-x32.o:vclock_gettime.c:function do_hres:
       error: relocation overflow: reference to 'hvclock_page'
    
       That's a known issue for years and the usual workaround is to disable
       CONFIG_X86_32
    
     - A recent build failure is caused by turning a relocation into an
       absolute one for unknown reasons. See link below.
    
     - There are a couple of gold workarounds applied already, but reports
       about broken builds with ld.gold keep coming in on a regular base and in
       most cases the root cause is unclear.
    
    In context of the most recent fail H.J. stated:
    
      "Since building a workable kernel for different kernel configurations
       isn't a requirement for gold, I don't recommend gold for kernel."
    
    So instead of dealing with attempts to duct tape gold support without
    understanding the root cause and without support from the gold folks, fail
    the build when gold is detected.
    
    Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
    Acked-by: default avatarPeter Zijlstra (Intel) <peterz@infradead.org>
    Acked-by: default avatarIngo Molnar <mingo@kernel.org>
    Link: https://lore.kernel.org/r/CAMe9rOqMqkQ0LNpm25yE_Yt0FKp05WmHOrwc0aRDb53miFKM+w@mail.gmail.com
    
    
    Reviewed-by: default avatarNathan Chancellor <natechancellor@gmail.com>
    Tested-by: default avatarNathan Chancellor <natechancellor@gmail.com>
    Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
    75959d44
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7