-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
Multi-lang builds of Pinecilv2 fail with ld/lto1 errors #1764
Comments
Rate of reproducing this issue locally - about 99%. But sometimes it's slightly different error every next time:
And it seems my fault after all, sorry! 😶TL; DR - probable root cause (mini write-up or today I learned):
I looked through logs before/after changes in While after the changes in Working on a fix now... |
I just added |
Neither did I so I never caught it 😓 |
Sure, no problem! Sorry to bring this bug in the first place to the repo. :| And I could be wrong in the terminology in root cause part but the bottom line is - as far as I could understand:
Something like that as far as I did manage to figure out this in a brief only to fix the issue in the most fast & suitable way. |
This does make sense, but also makes it hairy to debug 😓 |
Describe the bug
Multi-lang builds for
Pinecilv2
fail withld
/lto1
errors.To Reproduce
Expected behavior
Successful multi-lang builds for
PinecilV2
.Details of your device:
Build problem, not a device one.
Additional context
I create this issue to:
If you work on your branch in forked repo and see similar problem, please, add comment providing:
Here are the examples of this issue:
lto1 error / upstream:
lto1 error / branch:
ld error / branch:
lto1 error / branch:
At first, I couldn't reproduce it locally, not without
-j$(nproc)
at all nor with-j4
(since it's the value ofnproc
on my system). But when I did put-j2
which seems the case with github CI, I got interesting result almost right away:Binary files mentioned in the log above can be found here.
My further plan is to:
-j
, with-j2
, and with-j4
to see the behavior;make
:make -C source multi_...
vsmake multi_...
vscd source && make multi_...
(I doubt that this could be the reason but just to exclude the probability that it somehow related to changing build job command for respective build on github CI).My current suspicious that it probably may be somehow related to parallel building creating race condition-like situation (i.e. some binary file is not fully generated yet when some related dependency in a target inside
Makefile
"thinks" that it's ready.Less (but not impossible BTW) it could be a bug in the toolchain.
The text was updated successfully, but these errors were encountered: