-
Notifications
You must be signed in to change notification settings - Fork 13
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
Apple filesystem issues with abuild #21
Comments
Have reproduced. Looking into it. |
This appears to be only with the untarring of the source tarball -- subsequent to that, the package builds just fine (except for some failing tests). Still investigating... |
Ok. Problem appears to be that the ordering of files in the tarball has the symlink Will look into what's actually triggering the |
Right. This is a result of the A hacky workaround for this package might be to create the target by hand during the I'm following up to see if there's an underlying bug somewhere else. |
The suspicion is that this is a bug in the D4M filesystem interface code. I didn't manage to track it down, but did speak with a (now ex-) colleague at Docker about it and I understand that there's work in the pipeline that might fix it. Am going to close this issue now as it's out of my hands -- I don't think there's anything I can do to work around it automatically. |
When you try to build a package which uses special filesystem features on MacOS abuild with error.
To reproduce one can build bash and it will error.
The text was updated successfully, but these errors were encountered: