Opened 12 years ago
Closed 12 years ago
#38665 closed defect (fixed)
Dsniff fails to build on 10.7
Reported by: | michael.komm@… | Owned by: | ci42 |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | neverpanic (Clemens Lang) | |
Port: | dsniff |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Dsniff fails to compile on Lion. I think the problem is somewhere in DB library
port install dsniff ---> Computing dependencies for dsniff ---> Building dsniff Error: org.macports.build for port dsniff returned: command execution failed Please see the log file for port dsniff for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_dsniff/dsniff/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port dsniff failed
When I run make manually, I get errors linked to the DB library:
/record.c:130:30: error: use of undeclared identifier 'R_NOOVERWRITE' if (db->put(db, key, &data, R_NOOVERWRITE) == 0) ^ ./record.c:143:13: error: no member named 'seq' in 'struct __db' while (db->seq(db, &key, &data, R_NEXT) == 0) { ~~ ^ ./record.c:143:34: error: use of undeclared identifier 'R_NEXT' while (db->seq(db, &key, &data, R_NEXT) == 0) {
and also some linked to NFS:
In file included from ./filesnarf.c:28: ./nfs_prot.h:6:2: error: unterminated conditional directive #ifndef _NFS_PROT_H_RPCGEN ^ ./filesnarf.c:38:12: error: use of undeclared identifier 'NFS3_FHSIZE' u_char fh[NFS3_FHSIZE];
Attachments (2)
Change History (21)
Changed 12 years ago by michael.komm@…
comment:1 follow-up: 3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to cal@… |
comment:3 Changed 12 years ago by ci42
Replying to ryandesign@…:
I don't think anybody has been able to build dsniff for years; see #23971, though your errors look different.
I was able to build dsniff successfully just now.
comment:4 follow-up: 9 Changed 12 years ago by cooljeanius (Eric Gallager)
Replying to ciserlohn@…:
Dsniff doesn't like clang. Fixed in r104860.
If it doesn't like clang, shouldn't the blacklist be for all clang
s?
comment:5 follow-ups: 7 10 Changed 12 years ago by michael.komm@…
I have reinstalled libnids with libnet11 and tried to install dsniff-devel but the errors look quite the same
comment:6 Changed 12 years ago by michael.komm@…
I believe that dsniff is missing some header files from DB, although I have installed db53 package.
comment:7 Changed 12 years ago by ci42
Replying to michael.komm@…:
I have reinstalled libnids with libnet11 and tried to install dsniff-devel but the errors look quite the same
Please do a:
$ sudo port selfupdate
and try installing dsniff again. It should be fixed now.
comment:8 follow-up: 11 Changed 12 years ago by michael.komm@…
I did selfupdate and upgrade outdated but I am still getting the same errors
comment:9 Changed 12 years ago by ci42
Replying to egall@…:
Replying to ciserlohn@…:
Dsniff doesn't like clang. Fixed in r104860.
If it doesn't like clang, shouldn't the blacklist be for all
clang
s?
Yep, done in r104862.
comment:10 Changed 12 years ago by ci42
Replying to michael.komm@…:
I have reinstalled libnids with libnet11 and tried to install dsniff-devel but the errors look quite the same
dsniff-devel doesn't like clang, too. Fixed in r104862.
comment:11 Changed 12 years ago by ci42
Replying to michael.komm@…:
I did selfupdate and upgrade outdated but I am still getting the same errors
I blacklisted all clang versions for dsniff and dsniff-devel in r104862. Both work on my 10.7 machine now (I was able to reproduce the error you reported before). Please wait a little while, do a selfupdate and try installing dsniff or dsniff-devel again.
comment:12 Changed 12 years ago by michael.komm@…
I did the selfupdate again and now it builds all right. thanks a lot!
comment:13 Changed 12 years ago by ci42
dsniff-devel is now available as a binary package for 10.7. Provided you are using a standard MacPorts installation, you should be able to get a precompiled dsniff-devel:
$ sudo port selfupdate $ sudo port clean dsniff-devel $ sudo port -b install dsniff-devel
comment:14 Changed 12 years ago by ci42
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:15 Changed 12 years ago by neverpanic (Clemens Lang)
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:16 follow-up: 18 Changed 12 years ago by neverpanic (Clemens Lang)
Cc: | cal@… added |
---|---|
Owner: | changed from cal@… to ciserlohn@… |
Status: | reopened → new |
Your statement in comment:10 is incorrect. dsniff-devel
builds fine with clang for me. Please revert the change and find out why it doesn't work with your clang version, and if necessary blacklist a specific clang version.
comment:17 Changed 12 years ago by neverpanic (Clemens Lang)
And the same goes for dsniff
, it also works fine with my clang. Please also revert this change as falling back to llvm-gcc-4.2 should not be a long term solution considering it will go away in the next Xcode release. You can blacklist specific clang versions if necessary.
comment:18 Changed 12 years ago by ci42
Replying to cal@…:
Your statement in comment:10 is incorrect.
dsniff-devel
builds fine with clang for me. Please revert the change and find out why it doesn't work with your clang version, and if necessary blacklist a specific clang version.
You're right. I thought clang was causing the build failure when i saw the following line in the dsniff / dsniff-devel log file:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
But the build fails randomly regardless of using clang or not. There seems to be a timing problem.
comment:19 Changed 12 years ago by ci42
Resolution: | → fixed |
---|---|
Status: | new → closed |
The log is incomplete; please clean and try again.
I don't think anybody has been able to build dsniff for years; see #23971, though your errors look different.
Try dsniff-devel instead.