-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Build fails on macOS in Travis CI with 3.0.0 preview 7 - "dyld: lazy symbol binding failed: Symbol not found: _utimensat" #30346
Comments
Same issue for this PR too on macOS. |
Further digging found that the Travis macOS build was pinned to Removing this constraint (aspnet-contrib/AspNet.Security.OAuth.Providers@dbd0a96) fixed the issue. Leaving open for now as I'm not sure if this is an intentional change to the compatibility matrix for .NET Core 3.0 or not. |
Use the default XCode image version to resolve build failure relating to https://github.com/dotnet/corefx/issues/39701.
Introduced in dotnet/corefx#31522 /cc @Anipik @bartonjs @stephentoub Did we intend to drop support for OSX 10.12? Our docs say its still supported. |
macOS 10.12 is not supported: https://github.com/dotnet/core/blob/master/release-notes/3.0/3.0-supported-os.md. We just have too many redundant documentation sources. (@leecow we need to get https://docs.microsoft.com/en-US/dotnet/core/macos-prerequisites?tabs=netcore30 updated to say 10.13) |
Doc fixed. Thanks for the report. |
Use the default XCode image version to resolve build failure relating to https://github.com/dotnet/corefx/issues/39701.
I've been maintaining a branch of AspNet.Security.OpenId.Providers for ASP.NET Core 3.0 for a while, and just updated it from preview 6 to preview 7 (SDK version
3.0.100-preview7-012821
).The macOS build in Travis CI fails with the following error in preview 7 (build):
This failure appears right at the top of the build script with
dotnet build
.I've already updated several other branches from preview 6 to preview 7 with no issue, so it doesn't look like something systematic, but I'm not sure what specifically in this PR is causing the problem.
The text was updated successfully, but these errors were encountered: