On 4/26/07, Leslie Viljoen <leslieviljoen / gmail.com> wrote:
> On 4/26/07, Tim Pease <tim.pease / gmail.com> wrote:
> > On 4/26/07, Leslie Viljoen <leslieviljoen / gmail.com> wrote:
> > >
> > > Just tried RubyInline - amazing!
> > > I had one GCC hiccough on my Ubuntu 6 system, I had to do this:
> > >
> > > ln -s /usr/lib/gcc/x86_64-linux-gnu/4.0.3/cc1 /usr/bin/cc1plus
> > >
> > > ..to get GCC to recognise that G++ had been installed. Otherwise it
> > > gave me this:
> > > gcc: installation problem, cannot exec `cc1plus': No such file or directory
> > >
> >
> > The magic behind RubyInline is the rbconfig.rb file. This little Ruby
> > script contains the build environment used to compile the Ruby
> > interpreter for your particular platform. When RubyInline compiles
> > code, it uses the build environment found in rbconfig.rb.
> >
> > So, the catch is that your machine environment
> > (compilers/libraries/etc) needs to agree with what is in rbconfig.rb.
> >
> > For my Ruby/Cywin installation, rbconfig.rb can be found here ...
> >
> > /usr/lib/ruby/1.8/i386-cygwin/rbconfig.rb
> >
> > Blessings,
> > TwP
>
> Just installed the next Ubuntu, so I'll look at this. Thanks!

It just worked on Feisty, so they must have fixed the GCC installation.
Looked at rbconfig though. Thanks for the tip.

Les