# FastRI stopped seeing core/stdlib classes

**URL:** <https://www.ruby-forum.com/t/fastri-stopped-seeing-core-stdlib-classes/136212>\
**Category:** Ruby\
**Created:** [April 29, 2008, 9:04pm UTC](https://www.ruby-forum.com/t/fastri-stopped-seeing-core-stdlib-classes/136212 "2008-04-29T21:04:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shot\_SPiotr\_S.S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e79b87/32.png) [@Shot\_SPiotr\_S.S](https://www.ruby-forum.com/u/Shot_SPiotr_S.S)\
**Post date:** [April 29, 2008, 9:04pm UTC](https://www.ruby-forum.com/t/fastri-stopped-seeing-core-stdlib-classes/136212/1 "2008-04-29T21:04:02Z")

</div>

My setup: Ruby 1.8.6.p114 hand-compiled to ~/opt/ruby-1.8.6-p114.

I have a couple of other Ruby installs – Ubuntu’s Ruby 1.8.6.p111 at  
the proper FHS location(s), as well as JRuby 1.1.1, Ruby 1.8.7.preview2  
and Ruby 1.9.0-1 in ~/opt – but I don’t think this is the cause of the  
problem.

My problem: all of a sudden, FastRI (or RI, for that matter) stopped  
seeing core and stdlib classes. Running fastri-server -b and -B doesn’t  
help.

At first, this problem was common to all the Ruby installs (all with  
their respective FastRI gems), but I uninstalled all the fastri gems  
other than the 1.8.6.p114 one and the problem persists.

– Shot

---

<div class="post-metadata">

**Author:** ![Shot\_SPiotr\_S.S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e79b87/32.png) [@Shot\_SPiotr\_S.S](https://www.ruby-forum.com/u/Shot_SPiotr_S.S)\
**Post date:** [May 22, 2008, 11:53pm UTC](https://www.ruby-forum.com/t/fastri-stopped-seeing-core-stdlib-classes/136212/2 "2008-05-22T23:53:50Z")

</div>

Did you ever figure out what was going on here? I have the same  
problem.

---

<div class="post-metadata">

**Author:** ![Shot\_SPiotr\_S.S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e79b87/32.png) [@Shot\_SPiotr\_S.S](https://www.ruby-forum.com/u/Shot_SPiotr_S.S)\
**Post date:** [May 23, 2008, 2:30am UTC](https://www.ruby-forum.com/t/fastri-stopped-seeing-core-stdlib-classes/136212/3 "2008-05-23T02:30:37Z")

</div>

Psyonic wrote:

> Did you ever figure out what was going on here? I have the same  
> problem.

Same here.  
It does see methods on those classes however.

Regards  
Stefan

---

<div class="post-metadata">

**Author:** ![Shot\_SPiotr\_S.S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e79b87/32.png) [@Shot\_SPiotr\_S.S](https://www.ruby-forum.com/u/Shot_SPiotr_S.S)\
**Post date:** [June 3, 2008, 11:58am UTC](https://www.ruby-forum.com/t/fastri-stopped-seeing-core-stdlib-classes/136212/4 "2008-06-03T11:58:47Z")

</div>

Psyonic:

> On Apr 29, 3:02 pm, “Shot (Piotr S.)” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > My problem: all of a sudden, FastRI (or RI, for that matter) stopped  
> > seeing core and stdlib classes. Running fastri-server -b and -B doesn’t  
> > help.

> Did you ever figure out what was going  
> on here? I have the same problem.

Yeah (and sorry for not following up).

What you need to do is to generate the Ruby docs with  
RDoc from the Ruby source. IIRC, `rdoc -R` worked for me.

You might also want to check out the -Y  
option and the rest described in `rdoc -h`. 🙂

– Shot