|
From: Gudmundson M. A <gud...@st...> - 2006-07-22 23:31:06
|
Yes I'm sure it's a compiler difference. It's really not a big problem, = but I will try compiling on a different machine on Monday when I'm in. -----Original Message----- From: vfe...@li... on behalf of Ivan = Beschastnikh Sent: Fri 7/21/2006 11:11 AM To: vfe...@li...; vfe...@li... Subject: Re: [vfer-devel] VFER-0.97 Released =20 This didn't seem to go through so I'm sending it again to the lists. -------- Original Message -------- Subject: Re: [vfer-users] [vfer-devel] VFER-0.97 Released Date: Thu, 20 Jul 2006 19:56:31 -0700 From: Ivan Beschastnikh <iv...@cs...> To: Gudmundson Mitchell A <gud...@st...> CC: <vfe...@li...>, = <vfe...@li...> =09 Hi Mitchell, Thanks for the note. However i'm able to fully compile the released =20 code on every type of OS. The Makefile now specifies std=3Dgnu99 =20 argument for gcc to use, perhaps you're using a different compiler or =20 an older version of gcc (3.3.4 works for me here) ? Under the C99 =20 standard you can declare variables in middle of the code blocks so =20 vfer_getsockname() should compile ok. Nikolaus added this function =20 and that's the programming style he uses in the VSL lib codes but it =20 shouldn't impact compilation as long as the std flag is honored I =20 believe. Can you try on another machine and\or with a different gcc =20 version ? thanks, ivan. On Jul 18, 2006, at 1:37 PM, Gudmundson Mitchell A wrote: > You might want to change the function vfer_getsockname to at least =20 > declare or declare and initialize the vfer_sock * sock before the =20 > first if test is done. I just downloaded the new release and did a =20 > make lib and got a complie error. Just thought I'd let you know. > > -Mitchell > > -----Original Message----- > From: vfe...@li... on behalf of Ivan =20 > Beschastnikh > Sent: Tue 7/18/2006 12:56 AM > To: vfe...@li...; vfe...@li... > Subject: [vfer-devel] VFER-0.97 Released > > Hello, > > We've finally got around to releasing VFER-0.97. This timely release > includes the long awaited delay based congestion control. The default > parameters are a GAIN of 8 packets/RTT and a TARGET queueing delay of > 8ms. The code has been run over LAN and WAN links and performs > relatively well for a user space implementation with experimental CC. > > The release also includes quite a number of changes to the VFER > protocol including data range vector nacks instead of fragment vector > nacks, an AVL binary tree delay history data structure, and one of > this summer of code's student's work implementing authentication and > encryption within VFER. That code still needs work but it has already > been merged into the main branch and testing is under way for the > next release which will include authentication support over existing > user SSH keys. Many bugs have been squashed and features added. There > are links to the sources .tar.gz file from the VFER website- http:// > vfer.sf.net > > > thanks all, > > ivan. -------------------------------------------------------------------------= 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=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ vfer-devel mailing list vfe...@li... https://lists.sourceforge.net/lists/listinfo/vfer-devel |