-
Notifications
You must be signed in to change notification settings - Fork 13.3k
jemalloc configuration may be broken #17168
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
Comments
What precisely is broken? Can iOS just not build? Why? Also, what do you mean by the May 8 and June 5 dates? We currently don't have a dependence on autotools, and there are certainly many of us that'd like to keep it that way! Do we just need to check in a new |
Sorry for not being clear enough, those are names of
Yep, that should be enough |
If you'd like, it's ok to disable jemalloc by default for ios (for rust). Otherwise this is why we prefer to upstream changes before including them in our own repos (for example rust-lang/jemalloc@5921ba7). |
The fun thing is that actually changes are upstreamed you can see if you scroll a bit in |
Aha! Well in that case, feel free to submit an updated configure script! |
Will do. My point for creating this issue is increasing awareness of problem for future |
I regenerated the |
Guys, I terribly sorry and apologize, but it is my fault in the end - it seems that iOS was deleted from upstream, from Apologies again. |
…r=lnicola Update `rust-analyzer` to use `windows-sys` crate I noticed that the `rust-analyzer` project already depends on `windows-sys`. This update merely replaces the remaining direct dependencies on the older `winapi` crate with `windows-sys` dependencies. Originally posted here: rust-lang#124578
92b0926 broke iOS build.
It happened because a new
jemalloc
branch was started over2014-05-08
instead of2014-06-05
. While the new branch has all the required features, they are disabled becauseconfigure
script is bundled.So either
configure
should be removed completely and constructed byautoconf
during build process as usually or it should be regenerated and checked in on the everyjemalloc
update. The latter perhaps requires a guide for contributors so they to be aware of the issue.The text was updated successfully, but these errors were encountered: