Opened 13 years ago
Last modified 6 years ago
#32034 new defect
snort: libsf_engine.dylib: No such file or directory
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | fyodor.vassiley@…, jf@…, calsaiwing@… | |
| Port: | snort |
Description
Actually trying to use snort produces the error message:
/opt/local/lib/snort_dynamicengine/libsf_engine.dylib: No such file or directory
as reported by Fyodor Vassiley with a reproduction recipe on the mailing list. snort installs the file libsf_engine.so there, but then later looks for libsf_engine.dylib, which isn't there. So it would be best if the libraries were installed with the correct .dylib extension in the first place.
Jean-Francois Gobin provided a patch on the mailing list, but it must be applied to the Makefile after the configure phase has run. I don't know if there's a way the patch could be done at the normal time, during the patch phase. Perhaps a patch to the configure script.
Attachments (1)
Change History (7)
comment:1 follow-up: 2 Changed 13 years ago by jmroot (Joshua Root)
Changed 13 years ago by jfgobin (Jean-François Gobin)
| Attachment: | macos-dylib.patch added |
|---|
Patch to run during patch phase
comment:2 Changed 13 years ago by jfgobin (Jean-François Gobin)
The attached file is a patch to run during patch phase. It modifies snort-2.9.0.5/src/dynamic-plugins/sf_engine/Makefile.in to add the relevant statements.
comment:4 Changed 11 years ago by mf2k (Frank Schima)
| Keywords: | haspatch removed |
|---|
This patch does not work against the current version of the Portfile.
comment:5 Changed 10 years ago by mf2k (Frank Schima)
| Owner: | changed from markd@… to macports-tickets@… |
|---|
markd has retired. See #44782.
comment:6 Changed 6 years ago by jmroot (Joshua Root)
Is this still a problem with the current version?
The OS doesn't actually care about the filename of libraries at all. It's just a convention to use .dylib for shared libraries, and .so is often used instead for dynamically loaded plugin-type files. You just have to link or call dlopen using the filename that is in fact there at runtime.