Hi Bojan, On 4/3/07, Bojan Smojver <[EMAIL PROTECTED]> wrote: > I noticed a few problems with this: > > - by default, configure prepares a static build - is there are technical > reason for this (my understanding is that most Unix and Linux flavours > prefer dynamic linking these days for variety of reasons)?
It's a long story, but basically, many people (myself included) have multiple copies of the same library installed and dynamic linking search paths aren't always flexible enough. It's particularly painful with libraries like libnet which aren't always backwards compatible. > - if --enable-dynamic-link is specified, incorrect library directories > are picked up (-L/usr/lib) instead of (-L/usr/lib64); this then may be > related to encoding of standard RPATHs into the binaries (an issue that > upsets Fedora's RPM build system) Should be easy to fix. http://tcpreplay.synfin.net/trac/ticket/143 > I briefly looked at detection mechanism in configure.in and it appears > that the code assumes that if there is stuff in /usr/include, then > shared libraries must be in /usr/lib, which is not true on 64-bit Linux > boxes (e.g. Fedora, RHEL). > > Any reason why AC_CHECK_HEADERS/AC_CHECK_LIB cannot be used for this, > before trying specific paths (i.e. /usr /usr/local etc.)? Honestly, I don't know. I just know enough autoconf to get by, but I'll definitely give it a try and see what happens. -- Aaron Turner http://synfin.net/ http://tcpreplay.synfin.net/ - Pcap editing & replay tools for Unix ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Tcpreplay-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
