Bug 378279

Summary:	net-firewall/iptables : add USE=static-libs support
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	New packages	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED OBSOLETE
Severity:	enhancement	CC:	vapier
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Agostino Sarubbo gentoo-dev

2011-08-08 10:59:59 UTC

This package installs also static libs ".a" please provide do add relative
USE. TIA

/usr/lib/libip4tc.a
/usr/lib/libip6tc.a
/usr/lib/libiptc.a
/usr/lib/libxtables.a
/usr/lib/libipq.a
/usr/lib/libxtables.so
/usr/lib/libiptc.so
/usr/lib/libipq.so
/usr/lib/libip6tc.so
/usr/lib/libip4tc.so

Comment 1 Peter Volkov (RETIRED) gentoo-dev

2011-09-03 13:24:16 UTC

I'm not sure we need this here. We build iptables with all modules statically linked in and thus we build it with --enable-static, that in turn enables build of static libs and I don't see any need for USE flag to remove already built static libs ... Another option is to patch build system and add --enable-static-libs to iptables...

Mike, what's your opinion here?

Comment 2 SpanKY gentoo-dev

2011-09-07 04:08:59 UTC

i dont know what you mean by "We build iptables with all modules statically linked in".  iptables binaries dynamically link with their own libraries afaics.

the reason for the hardcoded --enable-static is iptables is uncommon and uses AC_DISABLE_STATIC in configure.ac.  past policy said we always build shared and static libs, thuse --enable-static.

i'm fine with USE=static-libs support in iptables

Comment 3 SpanKY gentoo-dev

2013-04-27 10:00:50 UTC

was added at some point