public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	 libc-alpha@sourceware.org
Cc: caiyinyu <caiyinyu@loongson.cn>,
	Chenghua Xu <xuchenghua@loongson.cn>,
	 liuzhensong <liuzhensong@loongson.cn>,
	Lulu Cheng <chenglulu@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: Re: [PATCH v2 1/1] LoongArch: Add static PIE support
Date: Fri, 23 Sep 2022 23:24:39 +0800	[thread overview]
Message-ID: <0ec5d964aacade80ca63e51967e674edb5503621.camel@xry111.site> (raw)
In-Reply-To: <af13509b-9451-4695-ab67-4364d7efe564@linaro.org>

On Fri, 2022-09-23 at 10:23 -0300, Adhemerval Zanella Netto wrote:
> /home/azanella/Projects/glibc/build/loongarch64-linux-gnu-lp64d/libc.a(setlocale.o)(__libc_freeres_fn+0x144): error: R_LARCH_SOP_PUSH_TLS_GOT against [undefweak] `_nl_current_LC_COLLATE':
> Internal: Shouldn't be resolved to const.
> 
> Using --disable-default-pie avoids this build issue.

Ouch.  R_LARCH_SOP_PUSH_TLS_GOT is some outdated thing and binutils-2.40
will not produce anymore.  Instead of spending my time for fixing some
nasty bugs in the "legacy" binutils code, I'll just add another check to
see if GAS is also new enough in v3.

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

  reply	other threads:[~2022-09-23 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 11:16 [PATCH v2 0/1] " Xi Ruoyao
2022-09-23 11:16 ` [PATCH v2 1/1] " Xi Ruoyao
2022-09-23 13:23   ` Adhemerval Zanella Netto
2022-09-23 15:24     ` Xi Ruoyao [this message]
2022-09-24  1:18   ` liuzhensong

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=0ec5d964aacade80ca63e51967e674edb5503621.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=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).