# ParseTree problem on Ubuntu 7.4, GCC 4.1

**URL:** <https://www.ruby-forum.com/t/parsetree-problem-on-ubuntu-7-4-gcc-4-1/92526>\
**Category:** Ruby\
**Created:** [April 20, 2007, 10:33am UTC](https://www.ruby-forum.com/t/parsetree-problem-on-ubuntu-7-4-gcc-4-1/92526 "2007-04-20T10:33:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![samuelzx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/4491bb/32.png) [@samuelzx](https://www.ruby-forum.com/u/samuelzx)\
**Post date:** [April 20, 2007, 10:33am UTC](https://www.ruby-forum.com/t/parsetree-problem-on-ubuntu-7-4-gcc-4-1/92526/1 "2007-04-20T10:33:36Z")

</div>

Hi List,

I am having trouble using ParseTree 1.7 on my new Ubuntu system.

When I require ‘parse\_tree’, I get the following error:  
[http://pastie.caboo.se/55273](http://pastie.caboo.se/55273)

It seems like it can not find variuos development files. I am using GCC  
4.1. Should I install the corresponding source? I’m downloading it at  
the moment.

If not, any other suggestions?

I’m using:  
Ruby 1.8.5  
Rubygems 0.9

This is most frustrating. All help appreciated.

Xin

---

<div class="post-metadata">

**Author:** ![samuelzx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/4491bb/32.png) [@samuelzx](https://www.ruby-forum.com/u/samuelzx)\
**Post date:** [April 20, 2007, 11:31am UTC](https://www.ruby-forum.com/t/parsetree-problem-on-ubuntu-7-4-gcc-4-1/92526/2 "2007-04-20T11:31:10Z")

</div>

Xin Z. wrote:

> Hi List,
> 
> I am having trouble using ParseTree 1.7 on my new Ubuntu system.
> 
> When I require ‘parse\_tree’, I get the following error:  
> [Parked at Loopia](http://pastie.caboo.se/55273)
> 
> It seems like it can not find variuos development files. I am using GCC  
> 4.1. Should I install the corresponding source? I’m downloading it at  
> the moment.

Make sure ‘build-essential’ and ‘ruby1.8dev’ ubuntu packages are  
installed.

For me it seems to work:

peter@brain:~$ gcc --version  
gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4)  
Copyright (C) 2006 Free Software Foundation, Inc.  
This is free software; see the source for copying conditions. There is  
NO  
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR  
PURPOSE.

peter@brain:~$ ruby --version  
ruby 1.8.5 (2006-08-25) [i486-linux]  
peter@brain:~$ ruby  
ruby ruby1.8 rubyforge  
peter@brain:~$ gem --version  
0.9.0  
peter@brain:~$ sudo gem install parsetree  
Password:  
Need to update 12 gems from [http://gems.rubyforge.org](http://gems.rubyforge.org)  
…  
complete  
Successfully installed ParseTree-1.7.0  
Installing ri documentation for ParseTree-1.7.0…

lib/parse\_tree.rb:123:26: ‘:’ not followed by identified or operator

test/test\_parse\_tree.rb:70:50: ‘:’ not followed by identified or  
operator

test/test\_parse\_tree.rb:81:38: ‘:’ not followed by identified or  
operator  
Installing RDoc documentation for ParseTree-1.7.0…

lib/parse\_tree.rb:123:26: ‘:’ not followed by identified or operator

test/test\_parse\_tree.rb:70:50: ‘:’ not followed by identified or  
operator

test/test\_parse\_tree.rb:81:38: ‘:’ not followed by identified or  
operator

Cheers,  
Peter  
\_\_  
[http://www.rubyrailways.com](http://www.rubyrailways.com) :: Ruby and Web2.0 blog  
[http://scrubyt.org](http://scrubyt.org) :: Ruby web scraping framework  
[http://rubykitchensink.ca/](http://rubykitchensink.ca/) :: The indexed archive of all things Ruby.

---

<div class="post-metadata">

**Author:** ![samuelzx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/4491bb/32.png) [@samuelzx](https://www.ruby-forum.com/u/samuelzx)\
**Post date:** [April 20, 2007, 4:41pm UTC](https://www.ruby-forum.com/t/parsetree-problem-on-ubuntu-7-4-gcc-4-1/92526/3 "2007-04-20T16:41:22Z")

</div>

Well, oddly enough… though I am using x86\_64 I was running into a lot  
of compilation errors.  
I removed binutils, installed build-essential and binutils and then  
everything seemed to work.

this was a problem in a few beta’s but may have missed a fix before  
release. I believe there is already a bug noted.

- 

Mike