Skip to content

Update linker-tools-error-lnk1107.md as the description couldn't help me on resolving the linker error and could get the solution from stackoverflow#3578

Closed
chaitanyavaleti wants to merge 1 commit into
MicrosoftDocs:mainfrom
chaitanyavaleti:patch-2
Closed

Conversation

@chaitanyavaleti

Copy link
Copy Markdown

No description provided.

@PRMerger4

Copy link
Copy Markdown
Contributor

@chaitanyavaleti : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver

ktoliver commented Dec 9, 2021

Copy link
Copy Markdown
Contributor

#label:"aq-pr-triaged"

@PRMerger17 PRMerger17 added the aq-pr-triaged Tracking label for the PR review team label Dec 9, 2021
@colin-home

Copy link
Copy Markdown
Contributor

@chaitanyavaleti
Thanks for taking the time to make an update. While you're not wrong, neither is the existing suggestion, which matches the example. What LNK1107 really means is, the linker tried to link something that's not one of the expected input types (or if it is an expected input type, the file is corrupted.) The expected input file types are usually .obj or .lib files, or a compiled resource or manifest, Common unexpected files that cause this error are .dll files or source files. Sometimes the unexpected files appear on the linker command line because something is broken in the build process, so the options sent to link.exe are incorrect.

I'm not sure what to do with your update. It doesn't have enough context to provide a good solution (but to be fair, neither does the existing content.) Perhaps it's better to restate the problem as an issue first, then we can determine the best solution.

@colin-home

Copy link
Copy Markdown
Contributor

Closed, since this is covered by another update that should be visible on Monday.

@colin-home colin-home closed this Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants