[Bug libc/31136] New: LoongArch glibc does not provide libutil shared object, against LSB 5.0

[Bug libc/31136] New: LoongArch glibc does not provide libutil shared object, against LSB 5.0

[icenowy at aosc dot io]

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.

[Bug libc/31136] LoongArch glibc does not provide libutil shared object, against LSB 5.0

[fweimer at redhat dot com]

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.

[Bug libc/31136] LoongArch glibc does not provide libutil shared object, against LSB 5.0

[icenowy at aosc dot io]

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.

[Bug libc/31136] LoongArch glibc does not provide libutil shared object, against LSB 5.0

[schwab@linux-m68k.org]

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

--- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> ---
If it's only about dlopen/dlsym, then a dummy link libutil.so.1 -> libc.so.6
should solve that.

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

[Bug libc/31136] LoongArch glibc does not provide libutil shared object, against LSB 5.0

[xry111 at xry111 dot site]

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

Xi Ruoyao <xry111 at xry111 dot site> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at xry111 dot site

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