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
A-driverArea: rustc_driver that ties everything together into the `rustc` compilerA-linkageArea: linking into static, shared libraries and binariesE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
If the final output file is not writable we end up failing with a cryptic linker error and a dump of the gcc command line. This could largely be avoided by doing some check before running the linker.
The text was updated successfully, but these errors were encountered:
Maybe it's possible from the gcc error code to determine what the error was. That would potentially be less error prone than doing the check ahead of time.
Even if the final output file is not writable, the error message is working properly.
When I make output file in /usr/bin, the error message is "Could not write output : error opening output file"
A-driverArea: rustc_driver that ties everything together into the `rustc` compilerA-linkageArea: linking into static, shared libraries and binariesE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
If the final output file is not writable we end up failing with a cryptic linker error and a dump of the gcc command line. This could largely be avoided by doing some check before running the linker.
The text was updated successfully, but these errors were encountered: