public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "icenowy at aosc dot io" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31136] LoongArch glibc does not provide libutil shared object, against LSB 5.0 Date: Tue, 12 Dec 2023 14:30:20 +0000 [thread overview] Message-ID: <bug-31136-131-eSh9rRb5YY@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31136-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31136 Icenowy Zheng <icenowy at aosc dot io> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #2 from Icenowy Zheng <icenowy at aosc dot io> --- ISO/IEC 23360-1-2:2021 is not architecture specific, it corresponds to [1] , which is a "Generic" part instead of a architecture-specific part; and the define of libutil.so.1 here is thus architecture-neutral, and at least could get implemented on new architectures. [1] https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/book1.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-12 14:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-11 9:17 [Bug libc/31136] New: " icenowy at aosc dot io 2023-12-11 11:19 ` [Bug libc/31136] " fweimer at redhat dot com 2023-12-12 14:30 ` icenowy at aosc dot io [this message] 2023-12-12 14:48 ` schwab@linux-m68k.org 2023-12-25 16:46 ` xry111 at xry111 dot site
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=bug-31136-131-eSh9rRb5YY@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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).