Skip to content
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

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

Closed
Tembocs opened this issue May 27, 2019 · 14 comments
Closed

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

Tembocs opened this issue May 27, 2019 · 14 comments
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Help Wanted We encourage anyone to jump in on these. Issue-Question For questions or discussion Product-Meta The product is the management of the products. Resolution-Answered Related to questions that have been answered

Comments

@Tembocs
Copy link

Tembocs commented May 27, 2019

Trying to build from Windows 10 x64 using Visual Studio 2019 and got his error message.
unrecognized flag '-Yu' in 'p2'. This is from the current master branch. How do I resolve this? Is it something to do with UTF-8? What is the workaround then? Can't be applied to the whole repo? I have tried to search related issues without success with proposed solutions.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 27, 2019
@zadjii-msft
Copy link
Member

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

@zadjii-msft zadjii-msft added Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Question For questions or discussion Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Meta The product is the management of the products. labels May 28, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label May 28, 2019
@DHowett-MSFT DHowett-MSFT removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label May 28, 2019
@bjohnson-fsi
Copy link

bjohnson-fsi commented May 30, 2019

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

Full Error List:

image

@zadjii-msft zadjii-msft added the Help Wanted We encourage anyone to jump in on these. label May 30, 2019
@mmdanggg2
Copy link

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

@kopwei
Copy link

kopwei commented Jun 1, 2019

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.

@baget
Copy link

baget commented Jun 2, 2019

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

@braindef
Copy link

braindef commented Jun 4, 2019

i have the same Error...

@HimiSaber
Copy link

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

@boldcronie
Copy link

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.

@Tembocs
Copy link
Author

Tembocs commented Jun 7, 2019

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

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jun 7, 2019
@DHowett-MSFT DHowett-MSFT added Resolution-Answered Related to questions that have been answered and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Jun 10, 2019
@DHowett-MSFT
Copy link
Contributor

This will be fixed by #1012.

@ghost
Copy link

ghost commented Jun 17, 2019

I still have this error.

@oliver-ni
Copy link

@NycuRO did you try @HimiSaber's solution? Worked for me

@ghost
Copy link

ghost commented Jun 21, 2019

i fixed. but when i use ubuntuu profile i've got gray screen only.

@devinvisible
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Help Wanted We encourage anyone to jump in on these. Issue-Question For questions or discussion Product-Meta The product is the management of the products. Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests