#48123 closed defect (fixed)
after installing ngrep, "Could not open /opt/local/lib/libpcap.A.dylib" causes rebuild on every install
Reported by: | Tatsh (Andrew Udvare) | Owned by: | grace@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | neverpanic (Clemens Lang), ryandesign (Ryan Carsten Schmidt), kurthindenburg (Kurt Hindenburg) | |
Port: | ngrep |
Description
Since installing ngrep, I get this every time I run port install ...
:
---> Scanning binaries for linking errors Could not open /opt/local/lib/libpcap.A.dylib: Error opening or reading file (referenced from /opt/local/bin/ngrep) ---> Found 1 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order ngrep @1.45
Looking at the file, it exists and is readable.
lrwxr-xr-x 1 root admin 19 Apr 23 14:28 /opt/local/lib/libpcap.A.dylib -> libpcap.1.7.3.dylib
Also, file
shows appropriate output:
/opt/local/lib/libpcap.1.7.3.dylib: Mach-O 64-bit dynamically linked shared library x86_64
Change History (13)
comment:1 Changed 9 years ago by larryv (Lawrence Velázquez)
Cc: | cal@… added |
---|
comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
comment:3 Changed 9 years ago by Tatsh (Andrew Udvare)
$ ngrep -V ngrep: V1.45, $Revision: 1.93 $ $ port rev-upgrade ---> Scanning binaries for linking errors ---> No broken files found.
So I am unsure how to reproduce this but I have had this happen a few times when I run port upgrade outdated
or just install a new package.
comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
And you're sure it mentioned ngrep and libpcap each time? Or was it each time something different that rev-upgrade reported as broken?
comment:5 Changed 9 years ago by Tatsh (Andrew Udvare)
Very sure it has been ngrep every time. I have yet to reproduce this issue again (of course once I file a bug).
comment:6 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
It's been a couple weeks... Have you seen this problem again?
Have you checked your disk lately with Disk Utility?
comment:7 Changed 9 years ago by Tatsh (Andrew Udvare)
Not sure if I have seen this bug in the last 3 weeks. I have usually updated unattended once per week. Close, watch and re-open if I see this issue again?
comment:8 Changed 9 years ago by mf2k (Frank Schima)
Port: | ngrep added |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
comment:9 Changed 8 years ago by hasso.tepper@…
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
This is a real problem. The point is that ngrep registers libpcap as build dependency, but it's really a runtime one. So, if ngrep is the only port depending from libpcap from ports, 'port uninstall leaves" removes libpcap and leaves ngrep in a broken state. I assume this change is needed:
- depends_build port:libpcap + depends_lib port:libpcap
comment:10 Changed 8 years ago by mf2k (Frank Schima)
Owner: | changed from macports-tickets@… to grace@… |
---|---|
Status: | reopened → new |
comment:11 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Cc: | kurthindenburg added |
---|
comment:12 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Resolution: | → fixed |
---|---|
Status: | new → closed |
What happens if you run
ngrep
? For example, try running this:It works for me, and
sudo port rev-upgrade
doesn't show ngrep as broken on my system.