Opened 17 years ago

Closed 5 years ago

#12321 closed defect (fixed)

libnet and libnet11 conflict

Reported by: bahamat@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: jim@…, pmq@…, etherflan@…, nerdling (Jeremy Lavergne), ryandesign (Ryan Carsten Schmidt), vh3@…, kngspook@…, alexander.janssen@…, MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Port: libnet, libnet11

Description

I use both dsniff and arping for work, but dsniff depends on libnet and arping depends on libnet11. Libnet and libnet11 can't be installed simultaneously.

Change History (17)

comment:1 Changed 17 years ago by pmq@…

Cc: jim@… pmq@… bahamat@… added
Milestone: Port Bugs
Priority: BlockerImportant
Summary: dsniff depends on libnet, arping depends on libnet11BUG: libnet and libnet11 conflict

Cc'ing the libnet maintainer. Unless someone releases its private dsniff-on-libnet11 patch, we need to fix the ports just like apr/apr0.

comment:2 Changed 17 years ago by nox@…

Cc: jim@geovedi.com,pmq@macports.org,bahamat@digitalelf.netjim@geovedi.com, pmq@macports.org, bahamat@digitalelf.net
Priority: ImportantNormal
Version: 1.5.0

comment:3 Changed 15 years ago by jmroot (Joshua Root)

Cc: bahamat@… removed
Port: libnet libnet11 added

comment:4 Changed 15 years ago by etherflan@…

Cc: etherflan@… added

Cc Me!

comment:5 Changed 15 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:6 Changed 15 years ago by nerdling (Jeremy Lavergne)

Owner: changed from macports-tickets@… to snc@…
Status: newassigned

comment:7 Changed 15 years ago by nerdling (Jeremy Lavergne)

Cc: snc@… added
Owner: changed from snc@… to macports-tickets@…
Status: assignednew

comment:8 Changed 15 years ago by hsivank@…

Take a look here

comment:9 in reply to:  description Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Summary: BUG: libnet and libnet11 conflictlibnet and libnet11 conflict

Replying to bahamat@…:

Libnet and libnet11 can't be installed simultaneously.

For now, I have marked libnet and libnet11 as conflicting in r61736.

comment:10 Changed 14 years ago by vh3@…

Cc: vh3@… added

Cc Me!

comment:11 Changed 12 years ago by kngspook@…

Cc: kngspook@… added

Cc Me!

comment:12 Changed 11 years ago by nerdling (Jeremy Lavergne)

Have there been updates for packages that depend on libnet so they can handle libnet11? Libnet 1.2 is now available upstream: should I make another (conflicting) libnet12 so that people can upgrade when their packages are ready?

comment:13 Changed 10 years ago by alexander.janssen@…

Cc: alexander.janssen@… added

Cc Me!

comment:14 Changed 10 years ago by alexander.janssen@…

So now I seemed to have found something odd; libnet and libnids somehow don't work together. When I try linking an application using both, ld complains about unresolved symbols:

Undefined symbols for architecture x86_64:
  "_libnet_build_ipv4", referenced from:
      _nids_killtcp_seq in libnids.a(killtcp.o)
  "_libnet_build_tcp", referenced from:
      _nids_killtcp_seq in libnids.a(killtcp.o)
  "_libnet_init", referenced from:
      _raw_init in libnids.a(killtcp.o)
  "_libnet_write", referenced from:
      _nids_killtcp_seq in libnids.a(killtcp.o)
ld: symbol(s) not found for architecture x86_64

Something's really odd here. The symbols are there though:

$ file libnet.1.dylib
libnet.1.dylib: Mach-O 64-bit x86_64 dynamically linked shared library
delicious:lib ajanssen$ nm libnet.1.dylib | grep libnet_build_tcp
00000000000076a0 T _libnet_build_tcp
0000000000007960 T _libnet_build_tcp_options
000000000000e824 s _libnet_build_tcp_options.padding
delicious:lib ajanssen$ nm libnet.1.dylib | grep libnet_build_ipv4
0000000000004bd0 T _libnet_build_ipv4
0000000000005030 T _libnet_build_ipv4_options
delicious:lib ajanssen$ nm libnet.1.dylib | grep libnet_build_tcp
00000000000076a0 T _libnet_build_tcp
0000000000007960 T _libnet_build_tcp_options
000000000000e824 s _libnet_build_tcp_options.padding
delicious:lib ajanssen$ nm libnet.1.dylib | grep libnet_init
0000000000009af0 T _libnet_init
delicious:lib ajanssen$ nm libnet.1.dylib | grep libnet_write
000000000000c450 T _libnet_write
000000000000c9d0 T _libnet_write_link
000000000000c580 T _libnet_write_raw_ipv4
000000000000c650 T _libnet_write_raw_ipv6

Any idea what's going on here?

P.S.: I have the same issue with both variants, libnet and libnet11.

Last edited 10 years ago by alexander.janssen@… (previous) (diff)

comment:15 Changed 10 years ago by neverpanic (Clemens Lang)

What does your linker line look like? It seems like it's missing -lnet. If it contains -lnet -lnids try making that -lnet -lnids -lnet. Make sure you don't have a copy of libnids or libnet in /usr/local.

comment:16 Changed 5 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Cc: MarcusCalhoun-Lopez added

comment:17 Changed 5 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: fixed
Status: newclosed

Since libnet and libnet11 are correctly marked as conflicting, and arping and dsniff can now be installed simultaneously, the original reason for opening this ticket has been resolved.
Any subsequent issues should probably have their own tickets.

Note: See TracTickets for help on using tickets.