Hey Tammo,
thanks the patch helped to get buildr 1.3.5 running but I still have
problems, now there is a problem with the 'write' function? Maybe a more
general problem with my environment?
WinXP 32-bit
Ruby 1.8.7 p302
DevKit 3.4.5
I get following error message with 'buildr _1.3.5_ package test=no --trace'
mkdir -p C:/ODE/ode-1.3.4/dao-jpa-ojpa-derby/target/derby/jpadb
mkdir -p C:/ODE/ode-1.3.4/dao-jpa-ojpa-derby/target/derby/jpadb
Buildr aborted!
←[31mBad file descriptor←[0m
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:596:in `write'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:596:in `puts'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:596:in `trace'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:625:in `invoke_with_call_chain'
C:/Ruby187/lib/ruby/1.8/monitor.rb:242:in `synchronize'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:616:in `invoke_with_call_chain'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:611:in `invoke'
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in
`invoke_task'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:232:in `top_level'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:232:in `each'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:232:in `top_level'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:496:in `standard_exception_handling'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:223:in `top_level'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:138:in `run'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:496:in `standard_exception_handling'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/lib/buildr/core/appli
cation.rb:135:in `run'
C:/Ruby187/lib/ruby/gems/1.8/gems/buildr-1.3.5-x86-mswin32/bin/buildr:19
C:/Ruby187/bin/buildr:19:in `load'
C:/Ruby187/bin/buildr:19
Regards,
Florian
Am 21.09.2010 21:49, schrieb Tammo van Lessen:
Hi,
yeah, using buildr with 1.3.4 could be easier, I also had to patch my
buildr installation in order to get it run.
Please try to apply the following patch to buildr 1.3.5, that should
help:
http://svn.apache.org/viewvc/buildr/trunk/lib/buildr/packaging/version_requirement.rb?r1=917054&r2=917053&pathrev=917054
Best,
Tammo
On 21.09.2010 16:48, Florian Wagner - FloWSoft.de wrote:
`const_missing'
: uninitialized constant Gem::Requirement::OP_RE (NameError)
