-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Bootstrap compiler update for 1.35 release #58793
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
Conversation
@bors: r+ p=1 |
📌 Commit 71b865f99a627aaf78ab146bc899fe2153270e6e has been approved by |
May unblock other work, @bors p=5 |
⌛ Testing commit 71b865f99a627aaf78ab146bc899fe2153270e6e with merge 6c41cffea96c6cdfaab601081802c18ae14f34e8... |
💔 Test failed - checks-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@alexcrichton Any ideas on that error? Are we perhaps linking against the wrong LLVM some how?
|
cc @michaelwoerister as well since this deals with LLVM tests |
Hm my best guess is that by updating the bootstrap compiler the stage0 compiler we download has a libdir that's somehow getting leaked into |
Hm, it's probably more of the LLVM shenanigans with rpaths that I fixed the last time then. I'll look more into this tonight. |
71b865f
to
0467943
Compare
Somewhat concerning that we're only seeing this when updating the bootstrap compiler, but I suppose previously we were just linking against the wrong LLVM without knowing it. Concerning, but not much we can do, I suppose. @bors r=alexcrichton |
📌 Commit 0467943 has been approved by |
Bootstrap compiler update for 1.35 release r? @alexcrichton
☀️ Test successful - checks-travis, status-appveyor |
r? @alexcrichton