[
https://issues.apache.org/jira/browse/BUILDR-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617920#action_12617920
]
Assaf Arkin commented on BUILDR-111:
------------------------------------
Thanks.
I edited the wording on the second part, to explain why it happens. Is this
correct?
The culprit is having the Gem's binary directory show up in @[EMAIL PROTECTED]
For
example, Buildr's @bin/buildr@ includes this line:
{{{!sh
require 'buildr'
}}}
Under normal circumstances, this tells RubyGems to load @buildr.rb@ from
the Gem's library directory. When @RUBYLIB@ points to the Gem's @bin@
directory, it ends up loading itself repeatedly.
To solve this, remove Buildr's @bin@ directory from @[EMAIL PROTECTED]
Removing all
directories that you don't actually need is better (other Gems may have the
same problem).
> new entry for trouble shooting page
> -----------------------------------
>
> Key: BUILDR-111
> URL: https://issues.apache.org/jira/browse/BUILDR-111
> Project: Buildr
> Issue Type: Improvement
> Components: Site/documentation
> Reporter: Geoffrey Ruscoe
>
> Here is a patch for the troubleshooting.textile page. Hope this is good!
> Index: troubleshooting.textile
> ===================================================================
> --- troubleshooting.textile (revision 680684)
> +++ troubleshooting.textile (working copy)
> @@ -119,3 +119,20 @@
> end
> }}}
>
> +
> +h2. buildr fails to run after install with a "stack level too deep
> +(SystemStackError)" error
> +
> +A particular quirk of an existing ruby setup can cause problems when running
> +buildr. If a system already has several ruby directories that are in the
> +PATH, it is often nice (appropriate?) to have them in RUBYLIB as well (to be
> +able to require them). If there are several of them a user may decide that
> +RUBYLIB=$PATH is a good way to handle this (or some less automated method
> +that has the same effect).
> +
> +If you see an error running buildr that shows the "stack level too deep"
> +error, it is probably your RUBYLIB environment variable. Removing the bin
> +directories that have buildr in them is probably the solution. Removing all
> +directories that you don't actually need is probably the appropriate measure.
> +
> +
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
