public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <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: Mon, 11 Dec 2023 11:19:33 +0000	[thread overview]
Message-ID: <bug-31136-131-wZ9y0FWyjS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31136-131@http.sourceware.org/bugzilla/>

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
ISO/IEC 23360-1-2:2021 is architecture-specific, so you cannot achieve
compliance except with one of the described architectures.

I do not have access to the 2021 version, but unless they did substantial
updates (that are not reflected on the LSB web site), it mostly applies to
obsolete architectures no longer in use, and obsolete software versions.

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

  reply	other threads:[~2023-12-11 11:19 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 ` fweimer at redhat dot com [this message]
2023-12-12 14:30 ` [Bug libc/31136] " icenowy at aosc dot io
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-wZ9y0FWyjS@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: 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).