Modify

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#5175 closed defect (fixed)

tcpdump 3.9.8 links statically against libpcap, but libpcap.so is installed anyway

Reported by: thomas@… Owned by: developers
Priority: normal Milestone: Kamikaze 8.09.1
Component: packages Version: Trunk
Keywords: tcpdump libpcap static Cc:

Description

When building tcpdump 3.9.8 from the packages feed, it is linked statically against libpcap. This results in a big binary, but libpcap.so is installed anyway, so the code is duplicated.

This increases my squashfs size considerably, I have no idea how to fix it right now though.

Attachments (0)

Change History (7)

comment:1 Changed 9 years ago by anonymous

The problem seems to be that tcpdump checks for a "local libpcap" library in ../libpcap*/libpcap.a and if it is present, builds against it instead of -lpcap. "rm -f $(PKG_BUILD_DIR)/libpcap.a" in libpcap/Makefile seems to be a working quickfix.

comment:2 Changed 9 years ago by anonymous

This fix reduces the binary size from 783KB to 614KB and reduces my custom image size by one erase block (64KB).

comment:3 Changed 9 years ago by anonymous

The Freetz project solves the issue with the following patch: http://www.freetz.org/browser/trunk/make/tcpdump/patches/02-shared_pcap.patch

comment:4 Changed 9 years ago by thomas@…

It's probably better than my approach, but the server only gives a 500.

comment:5 Changed 9 years ago by thomas@…

Now it works and yes, that is the patch I would suggest to solve the problem in a clean way.

comment:6 Changed 9 years ago by agb

  • Resolution set to fixed
  • Status changed from new to closed

Similar patch committed to /packages/ in [16000] and /branches/packages_8.09/ in [16003]

Thanks for reporting.

comment:7 Changed 9 years ago by nico

  • Milestone changed from Kamikaze to Kamikaze 8.09.1

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.