Long-Term Supported Versions

    Functions changed info

    ---------------diffs in pkgconf_libpkgconf.so.3.0.0_abidiff.out:----------------

    Functions changes summary: 0 Removed, 1 Changed (4 filtered out), 0 Added functions

    Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

    1 function with some indirect sub-type change:

    [C]'function void pkgconf_client_dir_list_build(pkgconf_client_t*, const pkgconf_cross_personality_t*)' at client.c:61:1 has some indirect sub-type changes:

    parameter 2 of type 'const pkgconf_cross_personality_t*' has sub-type changes:
      in pointed to type 'const pkgconf_cross_personality_t':
        in unqualified underlying type 'typedef pkgconf_cross_personality_t' at libpkgconf.h:68:1:
          underlying type 'struct pkgconf_cross_personality_' at libpkgconf.h:196:1 changed:
            type size changed from 704 to 768 (in bits)
            1 data member insertion:
              'bool pkgconf_cross_personality_::want_default_static', at offset 704 (in bits) at libpkgconf.h:206:1

    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    Just a small problem.

    I can fix it online!

    Bug Type
    Specifications and Common Mistakes

    ● Misspellings or punctuation mistakes;

    ● Incorrect links, empty cells, or wrong formats;

    ● Chinese characters in English context;

    ● Minor inconsistencies between the UI and descriptions;

    ● Low writing fluency that does not affect understanding;

    ● Incorrect version numbers, including software package names and version numbers on the UI.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

    ● Unclear logic, such as missing classifications, items, and steps.


    ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

    ● Incorrect schematic or architecture diagrams;

    ● Incorrect commands or command parameters;

    ● Incorrect code;

    ● Commands inconsistent with the functions;

    ● Wrong screenshots.

    Risk Warnings

    ● Lack of risk warnings for operations that may damage the system or important data.

    Content Compliance

    ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

    ● Copyright infringement.

    How satisfied are you with this document

    Not satisfied at all
    Very satisfied
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份