On 2024-04-25 20:30, Philip Race wrote:
On 4/24/24 4:24 AM, Magnus Ihse Bursie wrote:
That is a good question. libiconv is used only on macOS and AIX, for
a few libraries, as you say. I just tried removing -liconv from the
macOS dependencies and recompiled, just to see what would happen.
On 4/24/24 4:24 AM, Magnus Ihse Bursie wrote:
That is a good question. libiconv is used only on macOS and AIX, for a
few libraries, as you say. I just tried removing -liconv from the
macOS dependencies and recompiled, just to see what would happen.
There were three instances for macOS:
That is a good question. libiconv is used only on macOS and AIX, for a
few libraries, as you say. I just tried removing -liconv from the macOS
dependencies and recompiled, just to see what would happen. There were
three instances for macOS: libsplashscreen, libjdwp and libinstrument.
Out of
Du to a glibc security alert about a charset in iconv() I checked OpenJDK
(since I was quite sure encoding is handled in JCL), however there are a few
utilities (related to libinstrument and splash Screens) which use iconv.
If I see it correctly it’s mostly used for utf8 so it should not expose
