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

[x264] build failure #13350

Closed
nineKnight opened this issue Sep 4, 2020 · 3 comments
Closed

[x264] build failure #13350

nineKnight opened this issue Sep 4, 2020 · 3 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@nineKnight
Copy link

Host Environment

  • OS: latest Windows 10, no beta
  • Compiler: latest vs2019 and sdk. no beta

To Reproduce
Steps to reproduce the behavior:

git remote update
git pull
.\bootstrap-vcpkg.bat -disableMetrics
.\vcpkg.exe update
.\vcpkg.exe install x264:x64-windows

Failure logs
config-x64-windows-dbg-err.log
config-x64-windows-dbg-out.log

Additional context
The same problem since 46e25a1 while cdd4a98 is still working.

@abcping123
Copy link

Same as my issue #13327.
temporary solution: vcpkg_configure_make.cmake (line 223)
modify ;$ENV{SystemRoot}\\System32; => ;$ENV{SystemRoot}\\system32;

nineKnight referenced this issue Sep 5, 2020
…#13019)

* wip

Apply suggestions from code review

Co-authored-by: Alexander Neumann <[email protected]>

* [vcpkg_acquire_msys] Trim list of packages. Introduce defaults.

* [behaviortree-cpp] Fix dynamic dependency on ZMQ

Co-authored-by: Robert Schumacher <[email protected]>
Co-authored-by: Alexander Neumann <[email protected]>
Co-authored-by: Billy Robert O'Neal III <[email protected]>
@nico-abram
Copy link

nico-abram commented Sep 6, 2020

Just ran into this same problem

Thank you @abcping123 that fixed it!

EDIT: Sorry, as you mention in your issue, it doesn't actually fix it, just delays the fail to the install step

@NancyLi1013 NancyLi1013 added the category:port-bug The issue is with a library, which is something the port should already support label Sep 7, 2020
@NancyLi1013
Copy link
Contributor

Hi @nineKnight
Thanks for posting this issue.
Since it's duplicated to #13327, let's track this issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

No branches or pull requests

4 participants