Summary: | dev-ruby/plruby fails to build with PostgreSQL 9 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | PgSQL Bugs <pgsql-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ruby |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Diego Elio Pettenò (RETIRED)
2010-07-30 15:06:21 UTC
Created attachment 240713 [details]
Build log
>>> Configuring source in /var/tmp/portage/dev-ruby/plruby-0.5.4/work ...
* Running configure phase for ruby18 ...
/usr/bin/ruby18: no such file to load -- auto_gem (LoadError)
* ERROR: dev-ruby/plruby-0.5.4 failed:
mmh, naughty. Missing deps?
(In reply to comment #2) > >>> Configuring source in /var/tmp/portage/dev-ruby/plruby-0.5.4/work ... > * Running configure phase for ruby18 ... > /usr/bin/ruby18: no such file to load -- auto_gem (LoadError) Badly configured ruby environment. auto_gem should be installed as part of dev-lang/ruby. This error has nothing to do with plruby. No simply remember to reset the env when you jump into a chroot. You have Rubygems installed in the host but not WITHIN the chroot. (In reply to comment #4) > No simply remember to reset the env when you jump into a chroot. > > You have Rubygems installed in the host but not WITHIN the chroot. > I don't even know how it got there. With it gone things work "as expected" and I can reproduce the initial failure. plruby-0.5.4 builds fine here with PostgreSQL 9.0.4. I can't reproduce it either. Most likely explanation is that the beta version of postgres wasn't recognized. |