bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gold/18365] GOLD: AArch64: produces broken dynamic executable


From: shenhan at google dot com
Subject: [Bug gold/18365] GOLD: AArch64: produces broken dynamic executable
Date: Tue, 05 May 2015 18:52:33 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=18365

Han Shen <shenhan at google dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |shenhan at google dot com

--- Comment #6 from Han Shen <shenhan at google dot com> ---
Created attachment 8302
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8302&action=edit
conftest.dynamic built in shenhan's environment

This is the binary built on my environment by command - 

address@hidden:~/gold-bug$ cat shenhan.dynamic
GOLD=~/gold-aarch64/build/gold/ld-new

${GOLD} \
    --build-id \
    --no-add-needed \
    --eh-frame-hdr \
    --hash-style=gnu \
    -dynamic-linker /lib/ld-linux-aarch64.so.1 \
    -X \
    -EL \
    -maarch64linux \
    -fuse-ld=gold \
    -o conftest.dynamic \
    /usr/lib/gcc/aarch64-linux-gnu/4.8/../../../aarch64-linux-gnu/crt1.o \
    /usr/lib/gcc/aarch64-linux-gnu/4.8/../../../aarch64-linux-gnu/crti.o \
    /usr/lib/gcc/aarch64-linux-gnu/4.8/crtbegin.o \
    conftest.o \
    -L/usr/lib/gcc/aarch64-linux-gnu/4.8 \
    -L/usr/lib/gcc/aarch64-linux-gnu/4.8/../../../aarch64-linux-gnu \
    -L/usr/lib/gcc/aarch64-linux-gnu/4.8/../../../../lib
-L/lib/aarch64-linux-gnu \
    -L/lib/../lib -L/usr/lib/aarch64-linux-gnu \
    -L/usr/lib/../lib \
    -L/usr/lib/gcc/aarch64-linux-gnu/4.8/../../.. \
    -lgcc \
    --as-needed -lgcc_s --no-as-needed \
    -lc \
    -lgcc \
    --as-needed -lgcc_s --no-as-needed \
    /usr/lib/gcc/aarch64-linux-gnu/4.8/crtend.o \
    /usr/lib/gcc/aarch64-linux-gnu/4.8/../../../aarch64-linux-gnu/crtn.o

-- 
You are receiving this mail because:
You are on the CC list for the bug.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]