-
Notifications
You must be signed in to change notification settings - Fork 38
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
new libarchive31 fails test #1187
Comments
Is it reproducible? Is /sw/build.build on an external drive? What's the formatting on where ever /sw/build is? |
Reproducible. Everything's on the same drive, Mac OS Extended/Journaled, with no funny links. I do have BuildPath in a place outside of /sw/src/, but even undoing that setting does not change the result. |
Did the previous version pass tests (I don't know if it had that specific test)? Another thing would be if what ever is expected to make the hardlink is being shadowed by something else? coreutils-default? |
the libarchive build system can sometimes pick up dependencies outside of the specified installation prefix; maybe that has something to do with it? |
The previous version (3.4.0) was fine: 'link5b' is a newly added test. I have no 'coreutils-default' or older 'libarchive31' installed. This new test is conditional on
which is indeed available (unistd.h and libSystem). Version 3.4.0 did not look for that symbol. |
On 10.13, the newly committed libarchive31-3.7.7-1 has:
The .log reports:
The text was updated successfully, but these errors were encountered: