Is it necessary to specify that applications using glibc (libc.so) only use glibc?

What should I do to release the product in accordance with glibc's LGPL2 license for an application that meets the following requirements?

• The target application must be created with a dynamic link to run libc.so (so LGPL26b is satisfied).
• The application uses only the library provided by glibc.(Extreme story, printf only.Assume)
• The application itself is not a (L)GPL license (simply a commercial application).
• Allow reverse engineering as the application's own license. (LGPL 26)

Since glibc is an LGPL2 license,

You must include in each copy of the work a clear notice stating that the Library is used in the work and that its use is protected by this license.You must also provide a copy of this license.If a work displays a copyright notice at runtime, you must include a copyright notice in the Library and also include a reference to indicate to the user where a copy of this license is located.

I think it is necessary to
However, neither Mozila/FireFox nor LibraOffice have glibc in their license list.
The zip of info-zip dynamically links only glibc as far as objdump is concerned, but there is no mention of glibc in the license notation.

At first, I thought it was no longer (L)GPL due to a GCC runtime library exception, but I couldn't find a description that glibc was included in the GCC RLE.

Is glibc the only one with a special license?