How to pass skip-sanity-check to meson

[hxndg]

Hello, I'm writting a python lib with meson-python as build backend, I write a shell which wrapp sccache & gcc to debug for file permission issue when using meson, but meson keep telling me debug.sh is not a valid compiler, any method to pass skip-sanity-check to meson by meson-python?

[rgommers]

Hi @hxndg, I'm not sure I actually understand the question, I have never seen a Bash script wrapper like that. Using something like export CC = sccache $CC is common and works fine. I don't think you can or should prepend a debug.sh like that.

If you tell us what you're actually debugging in more detail, we can probably give a more helpful answer about how to go about that debugging.

[rgommers]

You said you had file permissions issues in the top post - that cannot really be the case on S3. A cache on S3 is either accessible to the user or it isn't, and there are separate permissions for "can the user download files". This is your AWS config (IAM policies etc.), a debug.sh script won't help you.

[hxndg]

You said you had file permissions issues in the top post - that cannot really be the case on S3. A cache on S3 is either accessible to the user or it isn't, and there are separate permissions for "can the user download files". This is your AWS config (IAM policies etc.), a debug.sh script won't help you.

Let me explain it, the permission issue is happended when nonroot user use gcc compile the .o file but sccache download cached .o file with wrong permission:

when root user start sccache server, it download the .o file from s3 with the root only rw permission. If a common user started to compile .o file using this root started sccache server, it can't overwrite the .o file, report a permission denied. .o file permission is something like this

-rw-r----- 1 root root 173456 10月 30 18:03 build/cp310/example_lib/example_generate_extension_module.cpython-310-x86_64-linux-gnu.so.p/meson-generated_example_generate_extension_module.c.o

I meet the problem when first use sudo uv pip install --system to install package to system, then use uv sync to install package to uv venv

[rgommers]

Ah okay, thanks for the content. I'd say just delete your cache and start over. Never ever use sudo uv pip install or sudo pip install.

[hxndg]

Ah okay, thanks for the content. I'd say just delete your cache and start over. Never ever use sudo uv pip install or sudo pip install.

Nmmmm, I walk around by settings root and common user use different sccache server.
So let's go back to the problem, is there any method to pass skip-sanity-check to meson?

[rgommers]

No, there isn't. If you define a compiler, it shouldn't be broken. The sanity check tells you that. There's no point circumventing that check, your build won't work anyway. Please just give up on that avenue, it won't help you.