-
Notifications
You must be signed in to change notification settings - Fork 3
Multiple artifacts and/or metadata files are declared at the same output location unpack.sh
#1
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
You need a newer version of buck that includes facebook/buck2@d56d60b, or you need to turn off |
Great, thanks! After using the latest nightly buck2, and doing some heroic fighting to get some sort of modern clang going on ubuntu:
I thought this was pretty fast compared to upstream, where I remember it taking > 20 minutes to compile, but it's been a long time since I did so. Today:
Not that I'm guessing "being faster" is a main goal of this project, just figured I'd toss in a comparison while I'm here. |
Your x.py only built stage1 not stage2. |
From my machine, here is a comparison of stage2 rustc build time, with download time split out because Cargo keeps crate downloads in a separate location that is not cleaned by x.py:
It's also interesting if you are building not just rustc but other tools, since Buck will happily build an arbitrary dependency graph concurrently while x.py is limited to building each different tool serially.
Some other sources of the Buck build being faster:
|
Ah, oops. Killing
|
First of all, very cool!
Second, I decided to give this a build on my machine. I'm using WSL, and I decided to try out dotslash:
When I try to
./buck2 run stage2:rustc -- --version --verbose
I get this:I'm still a newbie at starlark, so I'm not sure if this is something on my end, or maybe something where this doesn't yet handle WSL correctly?
The text was updated successfully, but these errors were encountered: