-
Notifications
You must be signed in to change notification settings - Fork 34
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
repro only uses one core to build #67
Comments
Two folded. |
I think repro should do the same as devtools and keep |
@FFY00 There is no host |
Check in |
Well yes. Pacman is packaged in several distros. I'd rather supply nproc or allow |
Yes, and why is it not acceptable to read And sorry, I messed up the order. I meant check |
The issue of defaulting to one core is that it's going to become a common gotcha because this becomes an extra step in the setup instructions of a rebuilder. People running rebuilders shouldn't be required to have the same level of experience as packagers. |
If packagers can't deal with this then we are all doomed. I am not thinking of any major reason why we couldn't read But anyway, it isn't a big deal. |
Repro isn't suppose to be used by packagers. But by users that want to reproduce their packages. |
Right, very well. I still think a build system flag to enable/disable this behavior is a good solution. But maybe we should just default to |
I'm not sure if this is intentional, due to makepkg or due to nspawn. Having all cores available would be great when rebuilding core since it contains multiple gcc packages. :)
The text was updated successfully, but these errors were encountered: