I have fixed this issue, and is scheduled for 4.1.0 beta1.
https://github.com/appneta/tcpreplay/issues/128
From: Fred Klassen <[email protected]<mailto:[email protected]>>
Reply-To: Main forum for tcpreplay
<[email protected]<mailto:[email protected]>>
Date: Wednesday, September 17, 2014 at 8:42 AM
To: Main forum for tcpreplay
<[email protected]<mailto:[email protected]>>
Subject: Re: [Tcpreplay-users] tcpreplay 4.0.5 won't configure soluition
I agree that default should remain static vs. dynamic. However, it would be
helpful to have it switch to dynamic automatically if no static libraries are
detected. Also help suggestion below may be helpful for those who do not
understand which files are the dynamic libraries.
I believe this actually is pointing out an issue with the described CentOS
distribution. If they distribute shared libraries they should also distribute
static (*.a) libraries.
I created a bug in GitHub so that this can be looked into for the next release.
https://github.com/appneta/tcpreplay/issues/128
Fred.
From: Wayne Marsh
<[email protected]<mailto:[email protected]>>
Reply-To: Main forum for tcpreplay
<[email protected]<mailto:[email protected]>>
Date: Wednesday, September 17, 2014 at 8:33 AM
To: Main forum for tcpreplay
<[email protected]<mailto:[email protected]>>
Subject: Re: [Tcpreplay-users] tcpreplay 4.0.5 won't configure soluition
I think the help could be a little more clear. Something along the lines of:
--enable-dynamic-link Use shared libraries ( .so and .dylib )
I imagine this is going to be required more often than not.
Maybe think about possibly changing the logic to:
--disable-dynamic-link
And enabling dynamic link by default.
This seems to be a back asswards way of doing it.
This seems to me like a release vs developer distribution issue. And the
solution employed is "--disable-debug" rather than "--enable-debug" in a stable
release.
On Wed, Sep 17, 2014 at 11:33 AM, Aaron Turner
<[email protected]<mailto:[email protected]>> wrote:
Based on what you're describing so far, I'd say "works as expected".
It probably would be a nice enhancement if configure auto detected the
missing static libraries and automatically switched to dynamic linking
though.
The reason for not defaulting to dynamic linking was because it tended
to create a much harder problem to debug when people had a mix of
libraries installed via packages & source.
--
Aaron Turner
http://synfin.net/ Twitter: @synfinatic
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
On Wed, Sep 17, 2014 at 7:07 AM, Wayne Marsh
<[email protected]<mailto:[email protected]>> wrote:
> I read the configure script and found out that the else condition of if
> $dynamic_link just prints that message.
>
> I then ran ./configure --enable-dynamic-link and everything configured
> properly.
>
> I still think this is a bug, just not as bad as initially though.
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Tcpreplay-users mailing list
> [email protected]<mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
> Support Information: http://tcpreplay.synfin.net/trac/wiki/Support
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Tcpreplay-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
Support Information: http://tcpreplay.synfin.net/trac/wiki/Support
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Tcpreplay-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
Support Information: http://tcpreplay.synfin.net/trac/wiki/Support
