Actions
Bug #10372
closedProblem with relative paths in update-gems makefile rule (common.mk)
    Bug #10372:
    Problem with relative paths in update-gems makefile rule (common.mk)
  
Description
When I do
make update-gems
I get the following error:
-e:1:in `require': cannot load such file -- downloader (LoadError)
uncommon.mk:1084: recipe for target 'update-gems' failed
make: *** [update-gems] Error 1
The reason for this seems to be a problem with relative paths.
The rule for update-gems in common.mk is as follows:
update-gems: PHONY
	$(ECHO) Downloading bundled gem files...
	$(Q) $(RUNRUBY) -I$(srcdir)/tool -rdownloader -answ \
	    -C "$(srcdir)/gems" \
	    -e 'gem, ver = *$$F' \
	    -e 'gem = "#{gem}-#{ver}.gem"' \
	    -e 'Downloader::RubyGems.download(gem)' \
	    bundled_gems
$(srcdir) is just '.', and so './tool' gets added to the load path, but then -C "$(srcdir)/gems" changes to the gems subdirectory, from which './tool' doesn't point to the tool directory anymore.
        
          
          Updated by hsbt (Hiroshi SHIBATA) about 11 years ago
          
          
        
        
      
      - Status changed from Open to Closed
 - % Done changed from 0 to 100
 
Applied in changeset r47899.
- common.mk: use relative load path for bundled_gems directory.
[Bug #10372][ruby-core:65630] 
        
          
          Updated by nobu (Nobuyoshi Nakada) about 11 years ago
          
          
        
        
      
      - Description updated (diff)
 - Status changed from Closed to Open
 
Which version of ruby are you using to download the files?
Since 1.9, -I directories are expanded to absolute paths.
        
          
          Updated by nobu (Nobuyoshi Nakada) about 11 years ago
          
          
        
        
      
      - Status changed from Open to Closed
 
Applied in changeset r47904.
common.mk: update-gems for older BASERUBY
- common.mk (update-gems): chdir to the target directory and then
add the tool directory to load paths, for older BASERUBY.
[Bug #10372][ruby-core:65630] 
        
          
          Updated by hsbt (Hiroshi SHIBATA) about 11 years ago
          
          
        
        
      
      I got same error with ruby trunk.
Actions