[Development] libQt6Core.so links against both libpcre.so.3 and libpcre2-16.so.0

[Shawn Rutledge]

On 8 Mar 2023, at 11:42, Shawn Rutledge via Development <development at qt-project.org> wrote:

My developer build:

$ lddtree /zhome/rutledge/dev/qt6-dbg/qtbase/lib/libQt6Core.so.6.2.0

Oops that was an old leftover; anyway it looks about the same in current dev branch:

/home/rutledge/dev/qt6-dbg/qtbase/lib/libQt6Core.so.6.6.0 (interpreter => /lib64/ld-linux-x86-64.so.2)
    libicui18n.so.72 => /usr/lib/libicui18n.so.72
    libicuuc.so.72 => /usr/lib/libicuuc.so.72
    libicudata.so.72 => /usr/lib/libicudata.so.72
    libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0
        libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0
    libz.so.1 => /usr/lib/libz.so.1
    libdouble-conversion.so.3 => /usr/lib/libdouble-conversion.so.3
    libb2.so.1 => /usr/lib/libb2.so.1
        libgomp.so.1 => /usr/lib/libgomp.so.1
    libpcre2-16.so.0 => /usr/lib/libpcre2-16.so.0
    libzstd.so.1 => /usr/lib/libzstd.so.1
    libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0
    libstdc++.so.6 => /usr/lib/libstdc++.so.6
    libm.so.6 => /usr/lib/libm.so.6
    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1
    libc.so.6 => /usr/lib/libc.so.6
    ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2

I guess it’s because QString uses 16-bit characters and libglib sticks with UTF8.  So how are Qt releases getting by without the 2-16 version then?  I guess those are built on RHEL 8.4 (?), which has available

/usr/lib64/libpcre16.so.0.2.10
/usr/lib64/libpcre2-8.so.0.7.1
/usr/lib64/libpcrecpp.so.0.0.1
/usr/lib64/libpcre2-16.so.0.7.1
/usr/lib64/libpcre2-posix.so.2.0.1
/usr/lib64/libpcreposix.so.0.0.6
/usr/lib64/libpcre2-32.so.0.7.1
/usr/lib64/libpcre32.so.0.0.10
/usr/lib64/libpcre.so.1.2.10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20230308/be21687a/attachment.htm>