mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Youling Tang <tangyouling@loongson.cn>
Cc: loongarch@lists.linux.dev, Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	linux-kernel@vger.kernel.org
Subject: Re: "kernel ade access" oops on LoongArch
Date: Wed, 15 Feb 2023 13:35:56 +0800	[thread overview]
Message-ID: <511d385675ea7a846ff791974c6ae7feeeec2589.camel@xry111.site> (raw)
In-Reply-To: <2e902dfa-cb84-7ef0-6b50-02b16354a139@loongson.cn>

On Wed, 2023-02-15 at 12:52 +0800, Youling Tang wrote:
> ../stdlib/stdlib.h:141:8: error: ‘_Float32’ does not name a type
>    141 | extern _Float32 strtof32 (const char *__restrict __nptr,
>        |        ^~~~~~~~

This is because Glibc expects GCC 13 to support _Float32, but early GCC
13 snapshots did not.

> /usr/bin/ld: /home/loongson/build_glibc/libc.a(dl-reloc-static-pie.o):
> in function `_dl_relocate_static_pie':
> /home/loongson/glibc/elf/dl-reloc-static-pie.c:44: undefined reference
> to `_DYNAMIC'

Oh, this one is my fault.  The check for compiler static PIE support was
not written correctly.  I'll fix it for Glibc later, but now you can
update GCC to the latest git master to proceed.
-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-02-15  5:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  8:46 Xi Ruoyao
2023-02-14 14:51 ` Huacai Chen
2023-02-15  4:52 ` Youling Tang
2023-02-15  5:35   ` Xi Ruoyao [this message]
2023-02-15  7:23     ` Youling Tang
2023-02-15  7:51       ` Jinyang He
2023-02-15  8:07         ` Xi Ruoyao
2023-02-15  8:25           ` Youling Tang
2023-02-15  8:35             ` Xi Ruoyao
2023-02-15 11:52               ` Xi Ruoyao
2023-02-15 12:51                 ` Xi Ruoyao
2023-02-15 13:06                   ` Xi Ruoyao

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=511d385675ea7a846ff791974c6ae7feeeec2589.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=chenhuacai@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=tangyouling@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

all inboxes | Powered by JetHome®