Re: Will the gold linker ever be NON Beta ?

["H.J. Lu" <hjl dot tools at gmail dot com>]

On Thu, Jun 22, 2017 at 12:38 PM, Cary Coutant <ccoutant@gmail.com> wrote:
>> You can't even use gold to build glibc master since glibc buiild
>> process modifies the default linker scripts to define some symbols
>> for sections and gold doesn't have a linker script to modify.
>> I created hjl/gold branch in glibc git repo so that linker script from
>> ld can be used with gold.
>
> What's on this branch that helps build glibc with gold? All I see
> there are a few new relocation overflow checks -- nothing to do with
> scripting.

hjl/gold branch is in GLIBC git repo, not binutils-gdb git repo.
                               ^^^^^^^^^
>> /usr/local/bin/ld.gold: warning: using 'GLIBC_2.2.5' as version for
>> 'getresuid' which is also named in version 'GLIBC_2.3.2' in script
>> /usr/local/bin/ld.gold: warning: using 'GLIBC_2.2.5' as version for
>> 'getresgid' which is also named in version 'GLIBC_2.3.2' in script
>> /usr/local/bin/ld.gold: warning: using 'GLIBC_2.2.5' as version for
>> 'setresuid' which is also named in version 'GLIBC_2.3.2' in script
>> /usr/local/bin/ld.gold: warning: using 'GLIBC_2.2.5' as version for
>> 'setresgid' which is also named in version 'GLIBC_2.3.2' in script
>
> What's causing these? Can you give me a simple repro?
>
>> /usr/local/bin/ld.gold: error:
>> /export/build/gnu/glibc-old/build-x86_64-linux/libc_pic.os.clean:
>> multiple definition of 'loc1'
>> /usr/local/bin/ld.gold:
>> /export/build/gnu/glibc-old/build-x86_64-linux/libc_pic.os.clean:
>> previous definition here
>> /usr/local/bin/ld.gold: error:
>> /export/build/gnu/glibc-old/build-x86_64-linux/libc_pic.os.clean:
>> multiple definition of 'loc2'
>> /usr/local/bin/ld.gold:
>> /export/build/gnu/glibc-old/build-x86_64-linux/libc_pic.os.clean:
>> previous definition here
>> /usr/local/bin/ld.gold: error:
>> /export/build/gnu/glibc-old/build-x86_64-linux/libc_pic.os.clean:
>> multiple definition of 'locs'
>> /usr/local/bin/ld.gold:
>> /export/build/gnu/glibc-old/build-x86_64-linux/libc_pic.os.clean:
>> previous definition here
>
> I'm guessing that these are caused by two identical copies of a symbol
> in the object file's symbol table. I thought I had to deal with that
> earlier, but perhaps I didn't catch all the cases -- what kind of
> input file is libc_pic.os.clean? And what's causing the duplicate
> symbols in the first place?
>
> -cary



-- 
H.J.