-
Notifications
You must be signed in to change notification settings - Fork 199
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
[NativeAOT] LINK : fatal error LNK1123 #1436
Comments
Are you able to build hello world sample on your machine? https://github.com/dotnet/runtimelab/tree/feature/NativeAOT/samples/HelloWorld |
I'll be able to test it out Monday morning and will let you know.
Thanks!
…On Fri, Aug 20, 2021, 16:11 Jan Kotas ***@***.***> wrote:
Are you able to build hello world sample on your machine?
https://github.com/dotnet/runtimelab/tree/feature/NativeAOT/samples/HelloWorld
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1436 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR6M6WI5APAVETJB5X23HLT52SF7ANCNFSM5CQSZNDQ>
.
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&utm_campaign=notification-email>
.
|
@jkotas, "Hello World" worked. |
Do you see If you would like to debug it yourself, I think that there is a problem |
Your question prompted me to look into the obj path and after not finding any .res file there I decided to delete everything in obj and bin and re-run the dotnet publish command. It worked! So I must assume that there was some garbage in there that confused the linker. Is there an ILC option to do a clean build every time? It's still not clear why the garbage/bad files (if it was in fact that) were generated and if has to do with VS2022 replacing 2019. It could be some inconsistency between a previous run using the 2019 toolchain and a later run of the publish command with the 2022 tooling. It might not be worthy to investigate it further though. Thanks for your help. (BTW, I had run Clean Solution from VS2022 before filing this issue, so I did not expect the obj/ bin/ folders to have any corruption.) |
There is not one. It is a general .NET SDK problem, not specific for ILC. It is a good idea to delete obj and bin directories after major toolset update. |
@dellamonica anything actionable left on your issue here? It seems to be it can be closed. |
Nothing I can think of. Thanks
…On Wed, Sep 8, 2021, 03:27 Andrii Kurdiumov ***@***.***> wrote:
@dellamonica <https://github.com/dellamonica> anything actionable left on
your issue here? It seems to be it can be closed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1436 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR6M6XHEQ6IVCSQ2VNQLZDUA366NANCNFSM5CQSZNDQ>
.
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>.
|
I have some problem, I clear all in obj folder of project ,It working fine again |
Me too... .NET SDK 7.0.103 |
You saved my day :) |
I'm getting the following error when trying to compile a project with the NativeAOT compiler.
Any suggestions?
The text was updated successfully, but these errors were encountered: