mattn / mattn/mruby-require

Does not compile due to rake problems

Open
#33 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
42
Forks
24
PR merge metrics
No merged PRs in 30d

Description

I get the following error below problems with rake when I try to use mruby-require as a gem in a gembox. This is with mruby v1.2.0. Any suggestions on how to resolve this?

```
bjorn@ancelot~/work/src/swita/build/src/mruby/build/mrbgems/mruby-require$ rake
(in /home/bjorn/work/src/swita/build/src/mruby)
rake aborted!
NoMethodError: undefined method `each' for nil:NilClass
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:310:in `block in generate_gem_table'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:290:in `each'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:290:in `each'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:309:in `generate_gem_table'
/home/bjorn/work/src/swita/build/src/mruby/mrbgems/mruby-test/mrbgem.rake:35:in `block in '
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:80:in `instance_eval'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:80:in `setup'
/home/bjorn/work/src/swita/build/src/mruby/build/mrbgems/mruby-require/mrbgem.rake:63:in `block (3 levels) in '
/home/bjorn/work/src/swita/build/src/mruby/build/mrbgems/mruby-require/mrbgem.rake:61:in `each'
/home/bjorn/work/src/swita/build/src/mruby/build/mrbgems/mruby-require/mrbgem.rake:61:in `block (2 levels) in '
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:13:in `instance_eval'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:13:in `block in each_target'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:12:in `each'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:12:in `each_target'
/home/bjorn/work/src/swita/build/src/mruby/build/mrbgems/mruby-require/mrbgem.rake:46:in `block in '
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:80:in `instance_eval'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:80:in `setup'
/home/bjorn/work/src/swita/build/src/mruby/tasks/ruby_ext.rake:41:in `block in to_proc'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:290:in `each'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgem_spec.rake:290:in `each'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgems.rake:4:in `block in '
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:13:in `instance_eval'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:13:in `block in each_target'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:12:in `each'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mruby_build.rake:12:in `each_target'
/home/bjorn/work/src/swita/build/src/mruby/tasks/mrbgems.rake:1:in `'
/home/bjorn/work/src/swita/build/src/mruby/Rakefile:26:in `load'
/home/bjorn/work/src/swita/build/src/mruby/Rakefile:26:in `'
/home/bjorn/.rvm/gems/ruby-2.3.0/gems/rake-11.2.2/exe/rake:27:in `'
/home/bjorn/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `eval'
/home/bjorn/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `'
(See full trace by running task with --trace)
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with mruby v1.2.0 and the mruby-require gembox using rake, then inspect tasks/mrbgem_spec.rake around lines 290-310. Trace the setup through mrbgems/mruby-test/mrbgem.rake:35 and build/mrbgems/mruby-require/mrbgem.rake:61-63. Done means the gem setup completes without the nil each error.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.