Opened 10 years ago
Closed 10 years ago
#44109 closed defect (invalid)
libarchive build error w/ missing acl
Reported by: | benedikt@… | Owned by: | tobypeterson |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.0 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | libarchive |
Description
When I run sudo port upgrade outdated libarchive fails to build. The build fails, because it is missing <acl/libacl.h> ( see the attached log file ). I've searched in the available ports for libacl, but found nothing that springs to my eye as missing dependency. Any ideas?
Attachments (1)
Change History (4)
Changed 10 years ago by benedikt@…
Attachment: | libarchive.log added |
---|
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Keywords: | libarchive acl lib acl removed |
Owner: | changed from macports-tickets@… to toby@… |
comment:2 Changed 10 years ago by benedikt@…
So I just renamed /usr/local/lib/libacl.dylib to libacl.dylib_bak and the build worked fine. The question is why is it there? Does it belong there? and how did it get there?
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Only you can answer how it got there.
We do not support having things installed in /usr/local when using MacPorts, because it causes problems like this. See wiki:FAQ#usrlocal. You should remove everything in /usr/local.
Note: See
TracTickets for help on using
tickets.
The interesting difference I see between my log (which completes the build successfully) and yours is this:
.log
noyesSo the question is: why does it find
acl_get_file
in-lacl
on your system? Where is libacl.a or libacl.dylib on your system, and how did it get there? What happens if you temporarily move or remove it, clean libarchive, and then try again?