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

Parameter to use fallback must be a directory not a file #61

Closed
andrewkatson opened this issue Jul 5, 2024 · 1 comment
Closed

Parameter to use fallback must be a directory not a file #61

andrewkatson opened this issue Jul 5, 2024 · 1 comment

Comments

@andrewkatson
Copy link

I posted a stack overflow: https://stackoverflow.com/questions/78713054/parameter-to-use-fallback-must-be-a-directory-not-a-file about this issue. Is it simply that MacOS doesn't support compilation because I tried sh_binary that runs a perl script and I get the same error. I am wondering if there is something with bazel sandboxing that is causing this because a shell script works and running the perl script works outside of bazel.

Parameter to use fallback must be a directory, not a file at /private/var/tmp/<redacted>/4e54a0e36f2fab506a36c4eeb929d5f5/execroot/_main/bazel-out/darwin_arm64-fastbuild/bin/configure_openssl.runfiles/_main/Configure line 20.
BEGIN failed--compilation aborted at /private/var/tmp/<redacted>/4e54a0e36f2fab506a36c4eeb929d5f5/execroot/_main/bazel-out/darwin_arm64-fastbuild/bin/configure_openssl.runfiles/_main/Configure line 20.
@andrewkatson
Copy link
Author

Okay I have figured it out. Configure looks for a specific path to a file named MODULES.txt not a directory generally speaking. And bazel moves that file when included in the data of whatever rule you use. So the solution is to modify Configure to look at the right path.

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

1 participant