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] New: LoongArch glibc does not provide libutil shared object, against LSB 5.0 Date: Mon, 11 Dec 2023 09:17:49 +0000 [thread overview] Message-ID: <bug-31136-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31136 Bug ID: 31136 Summary: LoongArch glibc does not provide libutil shared object, against LSB 5.0 Product: glibc Version: 2.40 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: icenowy at aosc dot io CC: drepper.fsp at gmail dot com Target Milestone: --- The Linux Standard Base Core Specification, Generic Part 5.0 (adapted as ISO/IEC 23360-1-2:2021) defines a libutil.so.1 shared object with 6 required functions, see [1]. However, as LoongArch is a new architecture introduced to glibc after the merging of auxiliary libraries to libc.so.6, it does not provide a libutil.so.1 at all, only libutil.a ; this breaks programs that tries to dlopen libutil.so.1 to access these 6 functions according to LSB. [1] https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/libutil.html -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-12-11 9:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-11 9:17 icenowy at aosc dot io [this message] 2023-12-11 11:19 ` [Bug libc/31136] " fweimer at redhat dot com 2023-12-12 14:30 ` 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@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).