-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
cpio: Cannot open: File name too long #125
Comments
The Vision file it's failing on must come from an Xcode version newer than what the current containers expect. It hasn't been tested against the latest Xcode with VisionOS SDK. The current tested version is Xcode 13.3.1: https://github.com/godotengine/build-containers/tree/3.x#toolchains |
That's the version I downloaded from Apple's website:
On the off-chance that the download went wrong, here's the SHA256 checksum for that file just in case:
|
I've just downloaded the file again on my MacBook, and it had the same checksum, so I can confirm that my original download was not corrupted. Maybe Apple has changed the file since I last downloaded it, but I'm not sure if that makes any sense. |
Now I'm super confused - are you sure the files that are producing errors come from future versions of Xcode? I've unpacked the |
Hey there! I'm currently trying to build the containers from the 3.x branch, but I'm running into an issue. When trying to build the OSX container, osxcross complains about there not being an SDK inside the
tarballs/
directory:After looking through the scripts, it looks like there should be a file at
files/MacOSX12.3.sdk.tar.xz
, but it doesn't exist on my system. I then checked to see where it is created, which is inDockerfile.xcode
. After seeing that it is run directly frombuild.sh
, I then checkedxcode_packer.log
, where I believe the source of the error is:From my understanding, this
cpio
error is stopping the Docker script from running, which is preventing the SDK file from being created, which ultimately causes the OSX container to fail.I'm not sure how to solve this, as I have not changed any of the docker files from the repository, but I had used these same files in December of last year, and March of this year, to build the containers. They worked in both of those instances, and the only thing that has changed is that I am now running Linux Mint instead of Fedora (although from my understanding, since these containers are using a specific Fedora base, I'm pretty sure the host system shouldn't matter?), unless the base image used for these containers has changed since? Any ideas as to how to solve this issue?
The text was updated successfully, but these errors were encountered: