-
Notifications
You must be signed in to change notification settings - Fork 483
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
Cannot fing type AtomicU128 error #645
Comments
This is the output when crossbeam/crossbeam-utils/build.rs Line 22 in 99c66ec
But I'm not sure why this is displayed to the user... I thought the content of the error on cc @cuviper |
Hmm, does firefox's build system seem to get and parse the output of build scripts? If the above assumptions are correct, this is a false positive of firefox's build system seem and probably could be fixed on firefox or autocfg side, but nothing on the crossbeam side. |
I'm trying to figure out what our tooling is doing, but I don't think that we can easily work around it. The way we parse errors is more involved than matching for "error", of course, but this one looks like it is produced by rustc so it is hard to distinguish it from normal build breaking errors by looking at the formatting. I hadn't realized that this is coming from autofcg which is outside of crossbeam. |
Moved this to cuviper/autocfg#30. |
Hi,
In Firefox's build system we are running into this error:
I am seeing it on a linux64 build, it might happen on other platforms as well.
It doesn't actually prevent the build from completing, but it confuses Firefox's build system and CI.
I'm not quite sure why this is happening. Is there a feature flag or something that could help with avoiding this error message, or something to adjust in crossbeam-utils?
The text was updated successfully, but these errors were encountered: