[mosh-devel] Fwd: Please test mosh 1.2 release candidate

[Reini Urban]

On 04/23/2012 07:50 PM, Keith Winstein wrote:
> fyi
> ---------- Forwarded message ----------
> From: Nick Mason<nmason at atlassian.com>
> Date: Mon, Apr 23, 2012 at 8:37 PM
> Subject: Re: [mosh-devel] Please test mosh 1.2 release candidate
> To: Keith Winstein<keithw at mit.edu>
>
>
> Hi Keith,
>
> Were you targeting CentOS 5 with this release? The build from source
> still doesn't work. :) It gets up to building in "network" then falls
> over:
>
>
> make[3]: Entering directory `/home/nmasonmosh-1.1.95/src/network'
>   CXX    network.o
>   CXX    networktransport.o
>   CXX    transportfragment.o
> transportfragment.cc:20:44: error: google/protobuf/io/gzip_stream.h:
> No such file or directory

So the question is: In which protobuf*-devel package is this missing 
header. I suspect the yum protobuf-2.3.0 package is too old.

I just tested mosh-1.1.96 ok on Centos 5.8, with protobuf-2.4.1 from 
source as there are no official centos5 protobuf packages.


> transportfragment.cc: In member function
> ‘TransportBuffers::Instruction
> Network::FragmentAssembly::get_assembly()’:
> transportfragment.cc:130: error: ‘GzipInputStream’ was not declared in
> this scope
> transportfragment.cc:130: error: expected `;' before ‘gzip_stream’
> transportfragment.cc:131: error: ‘gzip_stream’ was not declared in this scope
> transportfragment.cc: In member function
> ‘std::vector<Network::Fragment, std::allocator<Network::Fragment>  >
> Network::Fragmenter::make_fragments(const
> TransportBuffers::Instruction&, int)’:
> transportfragment.cc:175: error: ‘GzipOutputStream’ has not been declared
> transportfragment.cc:175: error: expected `;' before ‘gzip_options’
> transportfragment.cc:176: error: ‘gzip_options’ was not declared in this scope
> transportfragment.cc:176: error: ‘GzipOutputStream’ has not been declared
> transportfragment.cc:177: error: ‘GzipOutputStream’ was not declared
> in this scope
> transportfragment.cc:177: error: expected `;' before ‘gzip_stream’
> transportfragment.cc:178: error: ‘gzip_stream’ was not declared in this scope
> make[3]: *** [transportfragment.o] Error 1
> make[3]: Leaving directory `/home/nmasonmosh-1.1.95/src/network'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/nmasonmosh-1.1.95/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/nmasonmosh-1.1.95'
> make: *** [all] Error 2
>
>
> The protobuf, protobuf-devel, and protobuf-compiler packages are all
> installed (v2.3.0, according to yum).
>
> Cheers,
> Nick
>
>
>
> On 23/04/2012, at 14:05 , Keith Winstein wrote:
>
>> Hello all,
>>
>> Thanks for all your hard work on mosh! We have a release candidate for
>> mosh 1.2:
>>
>> https://github.com/downloads/keithw/mosh/mosh-1.1.95.tar.gz
>>
>> This is the first "post-deluge" release, and adds many improvements based
>> on our experience with mosh in the real world, including:
>>
>> * Helpful error messages for a variety of common problems
>>
>> * Locale passing in mosh (so less likely to get UTF-8-related errors)
>>
>> * Eliminates Boost and skalibs as dependencies
>>
>> * Fixes to build on FreeBSD, Cygwin, RHEL 5, OS X 10.5 on PPC
>>
>> * Improved responsiveness
>>
>> * Bugfixes and improvements re: terminal emulation and startup
>>
>> * Uses binary "hardening" compilation flags by default
>>
>> ===
>>
>> Please test the release candidate on your systems (and package managers)
>> and let us know of any problems. I'm particularly concerned that our
>> binary hardening flags may conflict with those on some distributions -- we
>> already had to override this on Ubuntu and I have heard reports that it
>> may also be a problem on Arch Linux.
>>
>> If all goes well, we should have mosh 1.2 by the end of the week.
>>
>> Thanks all,
>> Keith
>>
>> for the mosh developers
>> _______________________________________________
>> mosh-devel mailing list
>> mosh-devel at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/mosh-devel
>
> _______________________________________________
> mosh-devel mailing list
> mosh-devel at mit.edu
> http://mailman.mit.edu/mailman/listinfo/mosh-devel


-- 
Reini