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

new libarchive31 fails test #1187

Open
dmacks opened this issue Nov 14, 2024 · 5 comments
Open

new libarchive31 fails test #1187

dmacks opened this issue Nov 14, 2024 · 5 comments
Labels
waiting for reply Waiting for reply from submitter

Comments

@dmacks
Copy link
Member

dmacks commented Nov 14, 2024

On 10.13, the newly committed libarchive31-3.7.7-1 has:

The following tests FAILED:
	523 - libarchive_test_write_disk_hardlink (Failed)
Errors while running CTest

The .log reports:

test_write_disk_hardlink

/sw/build.build/libarchive31-3.7.7-1/libarchive-3.7.7/libarchive/test/test_write_disk_hardlink.c:205: 0 != r = archive_write_header(ad, ae)
      0=0 (0x0, 00)
      r = archive_write_header(ad, ae)=-25 (0xffffffffffffffe7, 01777777777777777777747)
    errno: 45
   detail: Can't create 'link5b'
/sw/build.build/libarchive31-3.7.7-1/libarchive-3.7.7/libarchive/test/test_write_disk_hardlink.c:256: File link5a has 1 links, expected 2
/sw/build.build/libarchive31-3.7.7-1/libarchive-3.7.7/libarchive/test/test_write_disk_hardlink.c:257: File should exist: link5b
/sw/build.build/libarchive31-3.7.7-1/libarchive-3.7.7/libarchive/test/test_write_disk_hardlink.c:257: Files link5a and link5b are not hardlinked
/sw/build.build/libarchive31-3.7.7-1/libarchive-3.7.7/libarchive/test/test_write_disk_hardlink.c:257: Summary: Failed 2 times
@nieder
Copy link
Member

nieder commented Nov 15, 2024

Is it reproducible? Is /sw/build.build on an external drive? What's the formatting on where ever /sw/build is?
It worked for me on 10.14.6/APFS

@dmacks
Copy link
Member Author

dmacks commented Nov 15, 2024

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.

@nieder
Copy link
Member

nieder commented Nov 16, 2024

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?

@nieder nieder added the waiting for reply Waiting for reply from submitter label Nov 26, 2024
@cooljeanius
Copy link

the libarchive build system can sometimes pick up dependencies outside of the specified installation prefix; maybe that has something to do with it?

@dmacks
Copy link
Member Author

dmacks commented Dec 17, 2024

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 HAVE_LINKAT. During the build:

-- Looking for linkat
-- Looking for linkat - found

which is indeed available (unistd.h and libSystem). Version 3.4.0 did not look for that symbol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for reply Waiting for reply from submitter
Projects
None yet
Development

No branches or pull requests

3 participants