-
Notifications
You must be signed in to change notification settings - Fork 57
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
Parallel Compilation Error #305
Comments
I presume this is not standalone build of TA? Which revision of TA is this? did you use Umpire is built using pure |
This is the build of TA done by LibChemist, which looks like it's pinned to a somewhat old version 1b7e2e3. Let me try master and see if I still have the problem. |
Looks like the error persists with master too. |
Could you please supply the full cmake args + invocation log?
…On Thu, Sep 2, 2021 at 5:08 PM Ryan Richard ***@***.***> wrote:
Looks like the error persists with master too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQXIZ3E522G5ARVBYJBISTT77RUVANCNFSM5DJV6GRQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
web: valeyev.net
|
I have been running into this too. For some reason, Umpire is trying to be built twice when the parallel builds happen. I think it may happen due to the separate Umpire-build and Umpire targets. At least, if I change the |
@ryanmrichard you should check if this fixes the problem you were encountering, but the referenced PR fixes this problem for all instances I've encountered |
When I try to build TA in parallel I sometimes get the error:
it's nothing show stopping, as running build again fixes the problem, but thought I'd let you know.
The text was updated successfully, but these errors were encountered: