-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Toolchain resolution seemingly failing and falling back to /usr/bin/gcc in some cases #48
Comments
More info: Here's the bazel version I'm using: Here's the working case I have so far:
Here's the non-working cases I have found so far:
|
Perhaps this is relevant: bazelbuild/bazel#12712 |
I have run into this once or twice, but haven't really been able to zero in on it and reproduce it once it starts working again.
What version of ubuntu are you running?
This should work, but I would recommend against using root for you builds for security reasons. Just as a hunch I would guess that this is something to do with how your bazelrc is being resolved with different users. Do you have a .bazelrc file in your workspace or in your home directory? The first thing I would try is to ensure that you have a
Or alternatively, just add If debugging the .bazelrc doesn't work would you mind posting a minimal set of steps to reproduce the problem i.e. basic workspace + Dockerfile etc? If the project is open source a URL should suffice. |
Ahh everything makes sense now... You were right... I inadvertently had a It's still interesting the Anyway, I'll go ahead and close this one out. |
I'm having trouble with the
bazel-embedded
rules in some cases. In a plain Ubuntu host, I can build my target with--platforms=@bazel_embedded//platforms:cortex_m7_fpu
and it works fine and invokesexternal/bazel_embedded/toolchains/gcc_arm_none_eabi/gcc_wrappers/nix/gcc
However when I run the same thing in a docker environment (based on Ubuntu) it attempts to use
/usr/bin/gcc
and fails because-mthumb
doesn't exist.I used the
--toolchain_resolution_debug
flag and interestingly, in both the working and non-working case it output the exact same thing (I diff'd and they were exactly the same):The text was updated successfully, but these errors were encountered: