Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introspector build fails for glib-based projects #11100

Open
jluebbe opened this issue Oct 10, 2023 · 1 comment
Open

Introspector build fails for glib-based projects #11100

jluebbe opened this issue Oct 10, 2023 · 1 comment
Assignees

Comments

@jluebbe
Copy link
Contributor

jluebbe commented Oct 10, 2023

The introspector build for glib itself fails with:

Step #6 - "compile-libfuzzer-introspector-x86_64": Checking if "GCC size_t typedef is long" compiles: NO
Step #6 - "compile-libfuzzer-introspector-x86_64": 
Step #6 - "compile-libfuzzer-introspector-x86_64": meson.build:1692:2: ERROR: Problem encountered: Could not determine size of size_t.
Step #6 - "compile-libfuzzer-introspector-x86_64": 
Step #6 - "compile-libfuzzer-introspector-x86_64": A full log can be found at /work/meson/meson-logs/meson-log.txt

Some other projects building glib as a meson subproject fail with the same issue:

Fuzz and coverage builds work fine, though.

For bluez, glib is built during the container creation instead of via build.sh, which avoids this issue.

The docs recommend static linking, but I'm not sure if there are benefits to compiling the subprojects with the sanitizer options.

How/where should this be fixed?

@DavidKorczynski DavidKorczynski self-assigned this Oct 10, 2023
@DavidKorczynski
Copy link
Collaborator

I suspect this is related to meson which have also been discussed in #7540 (comment) -- I need more looking into this though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants