#48409 closed defect (invalid)
sleuthkit: Directory /opt/local/var/macports/home/.ant/lib creation was not successful for an unknown reason
Reported by: | amadeus24 | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | chrstphrchvz (Christopher Chavez) | |
Port: | sleuthkit |
Description
Try to compile sleuth kit but failed because can't read the file "/opt/local/share/perl5.16/man/man3/Date::Manip::Zones.3pm", which is exist!
Attachments (2)
Change History (9)
Changed 9 years ago by amadeus24
comment:1 Changed 9 years ago by mf2k (Frank Schima)
Priority: | High → Normal |
---|
The Priority field is for use by Macports team members only.
comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | sleuth kit can't build removed |
---|---|
Owner: | changed from macports-tickets@… to jessekornblum@… |
Summary: | Building sleuthkit fail, while can't reading an existing file → sleuthkit: Directory /opt/local/var/macports/home/.ant/lib creation was not successful for an unknown reason |
Replying to ag@…:
Try to compile sleuth kit but failed because can't read the file "/opt/local/share/perl5.16/man/man3/Date::Manip::Zones.3pm", which is exist!
Ignore that error message; it is not the correct error message. MacPorts often prints the wrong final error message in the log. This is a bug in MacPorts base that we have not been able to determine the cause of.
The real error appears to be this one from earlier in the log:
Directory /opt/local/var/macports/home/.ant/lib creation was not successful for an unknown reason
comment:3 Changed 9 years ago by amadeus24
Create the directory but it seems to me there are more problems, even including write permission in the directory "/opt/local/var/macports/home/.ant/lib".
comment:4 Changed 9 years ago by mf2k (Frank Schima)
Owner: | changed from jessekornblum@… to macports-tickets@… |
---|
comment:5 Changed 4 years ago by chrstphrchvz (Christopher Chavez)
sleuthkit
has since been updated to 4.10.0. Is this ticket still relevant, or can it be closed?
comment:6 Changed 4 years ago by chrstphrchvz (Christopher Chavez)
Cc: | chrstphrchvz added |
---|
comment:7 Changed 4 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Please re-open the ticket and attach the latest main.log file if this is still an issue.
main.log