-
Notifications
You must be signed in to change notification settings - Fork 71
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
Failed to import repo as a third party dependency using bazel #61
Comments
Could you paste the exact error (or as much of it as you are able to share), wondering which files specifically are causing issues. We have a change coming through to the StableHLO BUILD file soon, if the issues are |
Sry my example is a bit misleading, basically there were two kinds of errors I met during compilation:
This kind of error only occures when mhlo libs are used as a third party dep. I didnt meet any problem when using stablehlo's targets. My solution is bacally what I wrote behind: to write a patch making all file includes use full path from mhlo root and remove all strip_include_prefix attr in BUILD file. b.
This one is much more non-intrusive since I can just write includes in own repo to mark td path like import MLIR using bazel. |
Hi there, we're currently working on a graph-compiler based on [some front graph]-mhlo-linalg-[some backend]. When we tried to use mhlo as a third party dependency in another repo as following BUILD:
An error occured in bazel build //target:this rule is missing dependency declarations for the following files.
I found out this error may caused by attr strip_include_prefix = "." in BUILD file, and the extensive use of this attribute seems due to file includes mainly for generated files.
https://github.com/tensorflow/mlir-hlo/blob/master/mhlo/IR/hlo_ops.cc#L87
Once all file includes are in full path, the problem is solved.
We are wondering that are these file includes written by some certain purpose for CMAKE(we tried bazel only), or they are just some known issues need to be rewrite in the future?
The text was updated successfully, but these errors were encountered: