Red Hat Bugzilla – Bug 248813
No libpcap.a in libpcap / libpcap.devel
Last modified: 2010-04-23 04:19:29 EDT
Description of problem:
There is no libpcap.a in libpcap/libpcap.devel
Version-Release number of selected component (if applicable):
[root@vel SPECS]# rpm -qa|sort|grep ^libpcap
Steps to Reproduce:
1. rpm -ql libpcap | grep libpcap\\.a
2. rpm -ql libpcap-devel | grep libpcap\\.a
libpcap.a not found
Consequently, ssldump 0.9b3-143 fails to build because of configuration script
looks for libpcap.a...
Very quick workaround to allow ssldump to build is >/usr/lib/libssl.a :-) to
make ssldump's autoconfiguration script happy and ssldump then happily builds
with libpcap.so. But this is not very nice and there is no chance to build
statically linked ssldump binary.
Fedora Packaging Guidelines strongly encourage not to ship static libs unless a
compelling reason exists (http://fedoraproject.org/wiki/Packaging/Guidelines).
The ssldump configure script should be fixed instead.
In that particular case, I can agree that ssldump's configure script should be
fixed, because of it is broken logic to check for .a file and then build
dynamically with .so.
I must also respect that there will be less and less static libraries shipped
with Fedora distribution.
On the other hand, the fact that static libraries are unavailable with Fedora,
is IMHO no good. Having -static packages as mentioned in the document referenced
by you would do much better. In fact, if you have some really huge software
project that produces huge and comlex executables consisting mainly of
application code, then statical linking does not add relatively much to them and
statically linked binary is the best way to get application running on more
systems, where single and small upgraded .so can break your the application
completely. (Of course, there are also known disadvantages of statical linking.)
And just for fun, here is a little snapshot taken on my small home installation
of F7. :-)
[root@vel tmp]# date
Thu Jul 19 12:19:29 CEST 2007
[root@vel tmp]# for a in `ls /usr/lib/*.a`; do p=`rpm -qf $a`; echo "$a $p";
done | grep \\.fc7$
Well, this topic was thoroughly discussed on fedora-devel list.
Please search the archives for "static linking" or have a look at:
Just for completeness: Package ssldump is part of Fedora 11+ and EPEL 4/5.
If I remember well, the last time i have checked Fedora source rpm, some patches, considered by me as "must have" were missing. Please take a look at (for example)
Eduard, if something is missing in the Fedora ssldump source RPM, please open
bug reports and tell exactly what is missing or wrong. I won't check a foreign
source RPM just because somebody mentions differences.
Robert: OK, I will do so, probably during the next weekend. I am so busy just now.
IMHO the main thing added by patches packaged in Suse source rpm is support for more ciphers. I have two or three patch sources for ssldump, so I will try to summarize.
now that ssldump-0.9-0.2.b3.fc12.i686 is out in F12 updates, I am happy to see that you did not resist sooner than I managed my time to allow me to look at it:
* Tue Apr 06 2010 Robert Scheck <firstname.lastname@example.org> 0.9-0.2.b3
- Added a patch to support AES cipher-suites (#248813 #c5)
- Added backporting patch from CVS 2006-06-19 (#248813 #c5)
I can only say thank you, that's it! And this means that I have just switched back to standard F12 ssldump as I have no longer reason to build my own openssl rpm.