-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
meson: error: unrecognized arguments: --fhead #pragma once #13834
Comments
Error when Meson is installed to
|
I can experience the same issue building GStreamer. |
Seems that the issue is the use of glib 2.82.2 |
|
That's wrong... |
Yeah it should be |
Reverting this patch https://gitlab.gnome.org/GNOME/glib/-/commit/013980d8398b1010c0e3414e5d1f06030fa557d2 in glib makes it work. |
I installed meson with pip instead of the meson installer MSI and it works now.
Here is the configure of glib: |
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but full_command. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but full_command. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but full_command. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but full_command. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
This seems to be a duplicate of #13804 |
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
This isn't a regression as meson hasn't ever done anything different here -- glib changed something and that change only worked on unix (but failed again on unix if someone built their own PyInstaller distribution of meson). |
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
In case of python and especially in the case of pyInstaller where the python command is meson.exe runpython, it should not be full path to be used but cmd_array. Fixing mesonbuild#13834
Describe the bug
Building many libraries (libsoup, harfbuzz) on Windows fails with similar error when meson is installed using the official installer (https://github.com/mesonbuild/meson/releases/download/1.6.0/meson-1.6.0-64.msi).
The errors does not occur when installing meson through pip.
From the error message, it looks like it does not properly parse the path when meson is installed to a path with spaces, installing meson to a path without space leads to slightly different error.
To Reproduce
Please include your
meson.build
files, preferably as a minimal toy example showing the issue.You may need to create simple source code files (don't include private/proprietary code).
Expected behavior
A clear and concise description of what you expected to happen.
system parameters
Is this a cross build or just a plain native build (for the same computer)?
Native
what operating system:
Windows 10
what Python version are you using:
3.13.0
what
meson --version
:1.6.0
what
ninja --version
if it's a Ninja build1.12.1
The text was updated successfully, but these errors were encountered: