Open yliu120 opened 7 years ago
For the record- this is under investigation
on the bazel side in https://github.com/bazelbuild/bazel/issues/4137.
If this turns out on rules_scala side or if we need to do a workaround in the meantime please ping us here
Thanks. I reported it here just because building rules_scala in a customized environment would result in this problem. I just let you guys know there is such an issue and you can keep this for a future reference. After my investigation, I found this is not related to rule_scala.
Thanks! I understand and appreciate getting us in the loop. I added the comment exactly for the same reason so that people coming here can find the relevant issue on Bazel itself. I'd really appreciate it if you could update here (and hopefully also close) when things progress on the other side.
On Sun, Nov 26, 2017 at 7:52 AM Yunlong Liu notifications@github.com wrote:
Thanks. I reported it here just because building rules_scala in a customized environment would result in this problem. I just let you guys know there is such an issue and you can keep this for a future reference. After my investigation, I found this is not related to rule_scala.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/bazelbuild/rules_scala/issues/346#issuecomment-346986262, or mute the thread https://github.com/notifications/unsubscribe-auth/ABUIF6Frx6sT31Vtirv0lc8l5voCO3Q9ks5s6PyGgaJpZM4QlEyb .
Please provide the following information. The more we know about your system and use case, the more easily and likely we can help.
Description of the problem / feature request / question:
I have a problem using bazel to build the rules_scala on a custom platform. I am sure it is because the shell envs are not propagated correctly to a subprocess that is spawned by some actions of bazel. Please see the log information that I provide in the last section.
If possible, provide a minimal example to reproduce the problem:
Environment info
Operating System: CentOS 6.7
Bazel version (output of
bazel info release
): 0.5.4If
bazel info release
returns "development version" or "(@non-git)", please tell us what source tree you compiled Bazel from; git commit hash is appreciated (git rev-parse HEAD
):Have you found anything relevant by searching the web?
(e.g. StackOverflow answers, GitHub issues, email threads on the
bazel-discuss
Google group)Anything else, information or logs or outputs that would be helpful?
(If they are large, please upload as attachment or provide link).
The command I ran to build rules_scala is
bazel build -s --verbose_failures --sandbox_debug //src/...
From the log message, you can see the first command doesn't have PATH and LD_LIBRARY_PATH propagated but the others have.