Unrecognized Flag '-Yu' in 'p2' #1031

Activity

1. ghost added

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on May 27, 2019
2. ghost added

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on May 27, 2019
3. zadjii-msft commented on May 28, 2019

   

   Mike Griese (zadjii-msft)

   on May 28, 2019

   Member

   More actions

   Could you give some more context on that error text? I've never seen it before.
4. Mike Griese (zadjii-msft)

   added

   Area-BuildIssues pertaining to the build system, CI, infrastructure, metaIssues pertaining to the build system, CI, infrastructure, meta

   Issue-QuestionFor questions or discussionFor questions or discussion

   Needs-Author-FeedbackThe original author of the issue/PR needs to come back and respond to somethingThe original author of the issue/PR needs to come back and respond to something

   Product-MetaThe product is the management of the products.The product is the management of the products.

   on May 28, 2019
5. ghost removed

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on May 28, 2019
6. Dustin L. Howett (MSFT) (DHowett-MSFT)

   removed

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on May 28, 2019
7. bjohnson-fsi commented on May 30, 2019

   

   bjohnson-fsi

   on May 30, 2019

   Last edited by bjohnson-fsi

   More actions

   Getting the same error when trying to build for x64 using Visual Studio 2019.

   Full Error List:

   

   👍React with 👍1Reacted by Marc jr. Landolt
8. Mike Griese (zadjii-msft)

   added

   Help WantedWe encourage anyone to jump in on these.We encourage anyone to jump in on these.

   on May 30, 2019
9. mmdanggg2 commented on Jun 1, 2019

   

   James Horsley (mmdanggg2)

   on Jun 1, 2019

   More actions

   I'm getting this too, trying to build x64 Release, Debug builds fine...
   

   👍React with 👍2Reacted by Marc jr. Landolt and Alberto Garcia Illera
10. kopwei commented on Jun 1, 2019

    

    kopwei (kopwei)

    on Jun 1, 2019

    Last edited by kopwei

    More actions

    The same. Debug x64 build passed but Release x64 failed with same issue.

    1>------ Build started: Project: TerminalConnection, Configuration: Release x64 ------
    1>LINK : fatal error C1007: unrecognized flag '-Yu' in 'p2'
    1>LINK : fatal error LNK1257: code generation failed
    1>Done building project "TerminalConnection.vcxproj" -- FAILED.
    2>------ Build started: Project: TerminalControl, Configuration: Release x64 ------
    2>LINK : fatal error C1007: unrecognized flag '-Yu' in 'p2'
    2>LINK : fatal error LNK1257: code generation failed
    2>Done building project "TerminalControl.vcxproj" -- FAILED.
11. baget commented on Jun 2, 2019

    

    Oren (baget)

    on Jun 2, 2019

    More actions

    Could you give some more context on that error text? I've never seen it before.

    I also saw this.

    • Clone the repro,
    • Update the submodules
    • Opened with VS2019
    • upgrade the solution
    • build the solution.

    This is the Error that I get

    27>------ Build started: Project: Host.unittest, Configuration: Release x64 ------
    25>readData.cpp
    27>precomp.cpp
    25>readDataDirect.cpp
    25>readDataRaw.cpp
    25>registry.cpp
    15>Nihilist.vcxproj -> D:\MyProjects\GitHub\terminal\\bin\x64\Release\Nihilist.exe
    24>LINK : fatal error C1007: unrecognized flag '-Yu' in 'p2'
    24>LINK : fatal error LNK1257: code generation failed
    

    👍React with 👍1Reacted by Marc jr. Landolt
12. braindef commented on Jun 4, 2019

    

    Marc jr. Landolt (braindef)

    on Jun 4, 2019

    More actions

    i have the same Error...
13. HimiSaber commented on Jun 4, 2019

    

    HimiSaber

    on Jun 4, 2019

    More actions

    Right click solution -->retarget solution，change to latest

    👍React with 👍4Reacted by Tembo, Terrell Green, Alberto Garcia Illera and DocNougat

    🎉React with 🎉3Reacted by boldcronie, Tembo and Alberto Garcia Illera
14. boldcronie commented on Jun 7, 2019

    

    boldcronie

    on Jun 7, 2019

    More actions

    I had the same error. VS2019/tools v142, and every build failed with at least two modules returning the "Unrecognized flag -Yu in p2" error. Re-targeted after clone, and individually re-targeted the UWP projects that didn't move from 141 to 142 during the initial re-target. Still got the errors during every build.

    Tried HimiSaber's solution -- after another failed build, right-clicked the OpenConsole.sln and clicked Re-target solution. That finished, so I built again. No errors! Launching the WindowsTerminal.exe still didn't work (would appear, then disappear after a few seconds), but I deployed anyway. Only took a few seconds, as the solution had been properly built. Checked Start Menu, and Windows Terminal (Dev Build) was there and working!

    Thank you HimiSaber! I almost didn't try it, as I'd already re-targeted several times.

    👍React with 👍2Reacted by Tembo and Terrell Green

    😄React with 😄1Reacted by Eliaxs1900

    🎉React with 🎉2Reacted by Tembo and Eliaxs1900
15. Tembocs commented on Jun 7, 2019

    

    Tembo (Tembocs)

    on Jun 7, 2019

    Author

    More actions

    HimiSaber and boldcronie, thank you so much this works. I have successful built WindowsTerminal and deploy. Its working and fast.
16. ghost added

    Needs-AttentionThe core contributors need to come back around and look at this ASAP.The core contributors need to come back around and look at this ASAP.

    on Jun 7, 2019
17. ghost removed

    Needs-Author-FeedbackThe original author of the issue/PR needs to come back and respond to somethingThe original author of the issue/PR needs to come back and respond to something

    on Jun 7, 2019
18. Dustin L. Howett (MSFT) (DHowett-MSFT)

    added

    Resolution-AnsweredRelated to questions that have been answeredRelated to questions that have been answered

    and removed

    Needs-AttentionThe core contributors need to come back around and look at this ASAP.The core contributors need to come back around and look at this ASAP.

    on Jun 10, 2019
19. DHowett-MSFT commented on Jun 10, 2019

    

    Dustin L. Howett (MSFT) (DHowett-MSFT)

    on Jun 10, 2019

    Contributor

    More actions

    This will be fixed by #1012.
20. Dustin L. Howett (MSFT) (DHowett-MSFT)

    closed this as completedon Jun 10, 2019
22. oliver-ni commented on Jun 21, 2019

    

    Oliver Ni (oliver-ni)

    on Jun 21, 2019

    More actions

    @NycuRO did you try HimiSaber's solution? Worked for me
24. devinvisible commented on Dec 7, 2020

    

    devINVISIBLE (devinvisible)

    on Dec 7, 2020

    More actions

    I had a similar issue in a completely unrelated project. Going into my project properties and setting Linker -> General -> Show Progress to /VERBOSE gave me a clue -- it showed a library of mine that it was searching for. A stack overflow comment suggested this was caused by this library being built with a different version of visual studio. I rebuilt both using the same version of visual studio (being mindful to build the appropriate architecture & release) and this error went away.