Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 10 Installation Error - RDoc parsing failure in qtruby4.rb #688

Closed
pchizek opened this issue Dec 11, 2017 · 3 comments
Closed

Windows 10 Installation Error - RDoc parsing failure in qtruby4.rb #688

pchizek opened this issue Dec 11, 2017 · 3 comments
Milestone

Comments

@pchizek
Copy link

@pchizek pchizek commented Dec 11, 2017

Error installing (what I assume is) a clean installation of COSMOS.
When running included batch file to install, runs fine until the following section.

...
Installing ri documentation for qtbindings-qt-4.8.6.4-x64-mingw32
Parsing documentation for qtbindings-4.8.6.4-x64-mingw32

RDoc::Parser::Ruby failure around line 100 of
lib/Qt/qtruby4.rb

Before reporting this, could you check that the file you're documenting
has proper syntax:

  C:/COSMOS/Vendor/Ruby/bin/ruby.exe -c lib/Qt/qtruby4.rb

RDoc is not a full Ruby parser and will fail when fed invalid ruby programs.

The internal error was:

        (RDoc::Error) Invalid class or module definition: Qt

ERROR:  While executing gem ... (RDoc::Error)
    Invalid class or module definition: Qt
ERROR: Problem installing cosmos gem
INSTALL FAILED
Press any key to continue . . .

Relevant Environment Variables:

Path = C:\COSMOS\Vendor\Ruby\bin: ...

Error has appeared on multiple installation attempts.

@jasonatball
Copy link
Collaborator

@jasonatball jasonatball commented Dec 11, 2017

This looks like an error between qtbindings and the new RDoc 6.0.0. I'm not sure how you got 6.0.0 since we're currently restricting it to >=3 and <5. I've determined anything prior to 6 will work. If you gem uninstall rdoc and then gem install rdoc --version 5 you should be good.

@jasonatball
Copy link
Collaborator

@jasonatball jasonatball commented Dec 11, 2017

You can verify your rdoc version by typing rdoc -v

@jasonatball
Copy link
Collaborator

@jasonatball jasonatball commented Dec 12, 2017

Looks like @ryanatball updated the installers to fix this with 95f35a2

@ryanatball ryanatball added this to the v4.2.2 milestone Apr 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants