public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Joseph Myers <joseph@codesourcery.com>,
	Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: caiyinyu <caiyinyu@loongson.cn>,
	libc-alpha@sourceware.org, Chenghua Xu <xuchenghua@loongson.cn>,
	Lulu Cheng <chenglulu@loongson.cn>, Wang Xuerui <i@xen0n.name>,
	liuzhensong <liuzhensong@loongson.cn>
Subject: Re: [PATCH v3 1/1] LoongArch: Add static PIE support
Date: Sun, 02 Oct 2022 22:25:11 +0800	[thread overview]
Message-ID: <607053080bd7db8d32a3696167efc6f52bcbc484.camel@xry111.site> (raw)
In-Reply-To: <04dfd5e79a0fa36458dc720d08095fec4ba737dc.camel@xry111.site>

On Sat, 2022-10-01 at 21:07 +0800, Xi Ruoyao wrote:
> On Fri, 2022-09-30 at 20:10 +0000, Joseph Myers wrote:
> > It appears this has broken the build with binutils 2.39 branch, the 
> > default used by build-many-glibcs.py.  Either the configure test
> > should be 
> > made stricter so it doesn't pass for binutils 2.39, or some relevant
> > bug 
> > fix should be backported to binutils 2.39 branch.
> > 
> > Building the glibc testsuite, the error is:
> > 
> > collect2: fatal error: ld terminated with signal 11 [Segmentation
> > fault], core dumped
> > compilation terminated.
> > ../Rules:301: recipe for target '/scratch/jmyers/glibc-
> > bot/build/glibcs/loongarch64-linux-gnu-
> > lp64d/glibc/elf/ifuncmain1static' failed
> > 
> > But it also causes the second GCC build in the build-many-glibcs.py 
> > "compilers" build to fail, if such a build is run with glibc
> > including
> > this change.
> 
> On my system I get a better error message:
> 
> /home/xry111/git-repos/glibc-t/install/compilers/loongarch64-linux-
> gnu-lp64d/sysroot/usr/lib64/crt1.o(.text+0x30): error:
> R_LARCH_SOP_PUSH_PCREL against `__libc_start_main@@GLIBC_2.36':
> PLT shouldn't be with r_addend.
> collect2: error: ld returned 1 exit status
> 
> Looks like crt1.o contains a PCREL relocation to __libc_start_main,
> despite it's not supported by binutils-2.39 and I expected that such a
> relocation should be only generated in rcrt1.o...  Will investigate.

Proposed fix at
https://sourceware.org/pipermail/libc-alpha/2022-October/142417.html.

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

      reply	other threads:[~2022-10-02 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24  7:45 [PATCH v3 0/1] " Xi Ruoyao
2022-09-24  7:45 ` [PATCH v3 1/1] " Xi Ruoyao
2022-09-29 13:32   ` caiyinyu
2022-09-30 12:47     ` Xi Ruoyao
2022-09-30 12:54       ` Adhemerval Zanella Netto
2022-09-30 13:55         ` Xi Ruoyao
2022-09-30 20:10         ` Joseph Myers
2022-10-01 13:07           ` Xi Ruoyao
2022-10-02 14:25             ` Xi Ruoyao [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=607053080bd7db8d32a3696167efc6f52bcbc484.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=adhemerval.zanella@linaro.org \
    --cc=caiyinyu@loongson.cn \
    --cc=chenglulu@loongson.cn \
    --cc=i@xen0n.name \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=liuzhensong@loongson.cn \
    --cc=xuchenghua@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).