-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Unable to build libgda on darwin due to itstool error #73762
Comments
Adding |
Sigh, it's always Darwin. I suggest using |
I would assume that help documentation is available online anyway, so it's a reasonable workaround. |
@FRidh I believe it's fundamentally disallowed, shell scripts cannot be intrepreters on the shebang in darwin. So going forward we'd need to have |
Yes, it's fundamentally not possible on Darwin. I know of this limitation and what needs to be done to improve the situation, however, we should not need to keep working around it. |
It's weird, because it seems to work fine for me on zsh:
It seems to be a limitation introduced by bash:
|
Ha! Changing the shebang to
All work fine:
|
Another option is to convert the wrapper script to am executable: http://www.datsi.fi.upm.es/~frosal/sources/shc.html |
About wrapping, have a look at #11133. |
The “shared-mime-info” package also fails to build on darwin due to “itstool” being broken. |
Thank you for your contributions.
|
This was fixed for 20.03. |
To Reproduce
Steps to reproduce the behavior:
Additional context
It looks like the itstool is being called with the wrong python.
Weirdly enough, the shebang looks right. If I call the tool directly, it works:
It's worth noting that it was working a month ago when I activated darwin support for libgda: #71200
It was also working fine last week, but I’m not sure exactly what changed in the mean time.
Metadata
"x86_64-darwin"
Darwin 19.0.0, macOS 10.15.1
no
no
nix-env (Nix) 2.3.1
"nixpkgs-20.03pre202062.84d582f4c6d"
/Users/seb/.nix-defexpr/channels/nixpkgs
Maintainer information:
The text was updated successfully, but these errors were encountered: