Opened 23 months ago
Closed 7 weeks ago
#59559 closed defect (duplicate)
dsniff @2.4b1_2: error: use of undeclared identifier 'R_NOOVERWRITE'
| Reported by: | dlamija (Muhammed Ramiza) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.2 |
| Keywords: | catalina | Cc: | ryandesign (Ryan Schmidt) |
| Port: | dsniff |
Description
found some error use of undeclared identifier 'R_NOOVERWRITE'
:info:build ./record.c:133:30: error: use of undeclared identifier 'R_NOOVERWRITE'
:info:build if (db->put(db, key, &data, R_NOOVERWRITE) == 0)
:info:build ^
:info:build ./record.c:146:13: error: no member named 'seq' in 'struct __db'
:info:build while (db->seq(db, &key, &data, R_NEXT) == 0) {
:info:build ~~ ^
:info:build ./record.c:146:34: error: use of undeclared identifier 'R_NEXT'
:info:build while (db->seq(db, &key, &data, R_NEXT) == 0) {
:info:build ^
all this error is related to db data structure : db.h?
on previous OS it has a problem detecting berkely DB 1.85 as installed db48 do not provide a relevant DB 1.85. But it's solved by installing db44 which is now deprecated in favour or db48
Attachments (1)
Change History (4)
Changed 23 months ago by dlamija (Muhammed Ramiza)
comment:1 Changed 23 months ago by jmroot (Joshua Root)
I'm not sure if it's worth trying to fix this version of dsniff, which dates from 2002. There seems to be a much newer (but still pretty old) python rewrite at https://github.com/dugsong/dsniff.
comment:2 Changed 23 months ago by ryandesign (Ryan Schmidt)
| Summary: | dsniff @2.4b1_2 failed to bulid on catalina 10.15.1 → dsniff @2.4b1_2: error: use of undeclared identifier 'R_NOOVERWRITE' |
|---|
comment:3 Changed 7 weeks ago by ryandesign (Ryan Schmidt)
| Cc: | ryandesign added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
This seems to be another flavor of the same problem reported in #58883. See https://www.monkey.org/~dugsong/dsniff/faq.html#Make%20dies%20with%20missing%20{{EX:R_NOOVERWRITE}}%20and%20{{EX:R_NEXT}}%20declarations. The answer there is:
Be sure to build Berkeley DB with
./configure --enable-compat185.
Presumably the OS BerkeleyDB is no longer built with this option. The MacPorts db ports aren't either, except for the db46 port which has an optional +compat185 variant. I guess we should delete the +compat185 variant and just turn that feature on unconditionally, and in as many other db ports as we have that support it.
main.log