You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, rustc's bootstrap uses cc to generate object file by asking it to generate a .a archive, discard the archive, and "guessing" where the temporary object files are to use them. Things like this. This, however, has been broken since either #684 or #786, as bootstrap does not understand the hashing mechanism used by cc-rs. This prevents upgrading cc in rustc's bootstrap, which is not ideal as cc has since included some bugfixes that are necessary to properly handle some situations (such as this).
I wonder if cc would accept a PR adding a public Build::compile_objects() function that would return a Vec<Path> of all the object files?
The text was updated successfully, but these errors were encountered:
Currently, rustc's bootstrap uses
cc
to generate object file by asking it to generate a.a
archive, discard the archive, and "guessing" where the temporary object files are to use them. Things like this. This, however, has been broken since either #684 or #786, as bootstrap does not understand the hashing mechanism used by cc-rs. This prevents upgrading cc in rustc's bootstrap, which is not ideal ascc
has since included some bugfixes that are necessary to properly handle some situations (such as this).I wonder if cc would accept a PR adding a public
Build::compile_objects()
function that would return aVec<Path>
of all the object files?The text was updated successfully, but these errors were encountered: