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

[harfbuzz] work around upstream SameFileError #16621

Merged

Conversation

Krzmbrzl
Copy link
Contributor

@Krzmbrzl Krzmbrzl commented Mar 9, 2021

During the configuration of harfbuzz several Python scripts are invoked
that are supposed to copy some files. For some reason however the
scripts end up being instructed to copy files to themselves at which
point a SameFileError is risen, causing the build to fail.

This is a workaround for the underlaying issue that is deemed to be
usptream. The upstream issues are

The workaround is to add a patch that makes sure these scripts check
whether source and target file are the same and only invoking the copy
action if they are not.

Fixes #16262

During the configuration of harfbuzz several Python scripts are invoked
that are supposed to copy some files. For some reason however the
scripts end up being instructed to copy files to themselves at which
point a SameFileError is risen, causing the build to fail.

This is a workaround for the underlaying issue that is deemed to be
usptream. The upstream issues are
- mesonbuild/meson#8375
- harfbuzz/harfbuzz#2870

The workaround is to add a patch that makes sure these scripts check
whether source and target file are the same and only invoking the copy
action if they are not.

Fixes microsoft#16262
@ghost
Copy link

ghost commented Mar 9, 2021

CLA assistant check
All CLA requirements met.

@JackBoosY JackBoosY added category:port-bug The issue is with a library, which is something the port should already support requires:discussion labels Mar 10, 2021
@JackBoosY
Copy link
Contributor

cc @Neumann-A for review this PR.

@Krzmbrzl
Copy link
Contributor Author

Maybe I should also mention that I proposed the same changes upstream, but they were neglected as they are only hiding the underlaying problem. While that is of course true, I think vcpkg should rather hide an upstream problem than to fail the build because of it ☝️

@Neumann-A
Copy link
Contributor

@JackBoosY LGTM if it works.

@Krzmbrzl
Copy link
Contributor Author

This worked at least for me on the machine (or rather VM) that did create the problems before. Haven't tested on any other system though 🤷

@ras0219-msft ras0219-msft merged commit 4634989 into microsoft:master Mar 11, 2021
@ras0219-msft
Copy link
Contributor

Agreed, LGTM. Thanks!

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

Successfully merging this pull request may close these issues.

[harfbuzz] build failure
4 participants