On 7/11/07, Francis Cianfrocca <garbagecat10 / gmail.com> wrote:
> The Eventmachine team is pleased to announce the release of version 0.8.0,
> available now on RubyForge as a tarball and as a gem.
>
> Eventmachine is a framework for writing fast, scalable network-aware
> programs (clients, servers, or both) in Ruby or C/C++, without requiring the
> use of threads. EM is used today in a variety of production systems
> including Web, mail, and LDAP/RADIUS servers, SNMP agents, and custom
> protocol handlers. It's also used in Kirk Haines's Swiftiply, a fast
> clustering proxy for Rails and other web frameworks.
>
> The 0.8.0 release adds automatic support for epoll, on Linux 2.6 kernels.
> This enables Eventmachine programs to break through Ruby's limit of 1024
> file and socket descriptors per process. In performance tests designed to
> simulate busy web servers, Eventmachine with epoll exhibits the behavior you
> would expect: with very large numbers (>20,000) of quiet connections and a
> few active ones, there is no noticeable degradation of responsiveness or
> total throughput, compared to cases with only a few connections.
>
> We expect the next major EM release to be called 0.9.0. It will add
> Erlang-like features intended to make it simple for EM-based programs to
> send messages to each other, or to other processes. A typical use case for
> this capability is a "service" web site that must make calls to other web
> sites, web services, or other network services in order to fulfill requests
> from its own clients.
>
> Thanks to all for your support of the EM project, and especially to Tony
> Arcieri, who tirelessly bugged me for weeks to add the epoll support, and to
> Kirk for helping to shake it out.
>

Just tried to compile EventMachine on a SPARC Solaris box here at
work.  g++ does not like the compiler flags that are meant for the
SUNWspro compilers :/

We are using the Blastwave packages for our Ruby install. That package
was compiled using the SUNWspro compilers, and so extconf.rb is
grabbing the CFLAGS from there. -KPIC makes g++ very unhappy.

I wish I was writing to say I have a patch for you, but that is not the case.

Any pointers from rubyland on how to get the correct CFLAGS into extconf.rb?

CONFIG["CFLAGS"] = " -O2 -fPIC"    # <-- doesn't seem to do the trick

I always end up with the CFLAGS meant for the SUNWspro compiler.

Blessings,
TwP