From cranky at transnexis.com Mon Aug 1 10:55:09 2005 From: cranky at transnexis.com (Andrew Cranson) Date: Mon Aug 1 10:49:19 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib Message-ID: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> Hi, When installing rubygems I get: /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib (LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/package.rb:9 from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/builder.rb:1 from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:61:in `manage_gems' ... 7 levels... from setup.rb:887:in `exec_install' from setup.rb:705:in `invoke' from setup.rb:674:in `invoke' from setup.rb:1352 Do you have any ideas what can be causing it? This is with rubygems-0.8.11, I've tried a few things but can't seem to get it working. Andrew From cranky at transnexis.com Mon Aug 1 10:58:10 2005 From: cranky at transnexis.com (Andrew Cranson) Date: Mon Aug 1 10:52:20 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> Message-ID: <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> Just to add, this is on RHEL3. Reply-To: rubygems-developers@rubyforge.org Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib To: rubygems-developers@rubyforge.org > Hi, > > When installing rubygems I get: > > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in > `require__': > No such file to load -- zlib > (LoadError) > from > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in > `require' > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/package.rb:9 > from > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in > `require__' > from > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in > `require' > from /usr/local/lib/ruby/site_ruby/1.8/rubygems/builder.rb:1 > from > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in > `require__' > from > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in > `require' > from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:61:in `manage_gems' > ... 7 levels... > from setup.rb:887:in `exec_install' > from setup.rb:705:in `invoke' > from setup.rb:674:in `invoke' > from setup.rb:1352 > > Do you have any ideas what can be causing it? This is with > rubygems-0.8.11, I've > tried a few things but can't seem to get it working. > > Andrew > > _______________________________________________ > Rubygems-developers mailing list > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers From halostatue at gmail.com Mon Aug 1 14:13:15 2005 From: halostatue at gmail.com (Austin Ziegler) Date: Mon Aug 1 14:07:26 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> Message-ID: <9e7db911050801111313b524bd@mail.gmail.com> On 8/1/05, Andrew Cranson wrote: > Just to add, this is on RHEL3. Some OS repackagers break Ruby. Debian used to be the worst culprit, but you'll want to make sure you have zlib and ruby-zlib (or something like that) installed, as these *are* parts of core Ruby but some folks don't see fit to install them with the core Ruby language. -austin -- Austin Ziegler * halostatue@gmail.com * Alternate: austin@halostatue.ca From cranky at transnexis.com Mon Aug 1 14:27:13 2005 From: cranky at transnexis.com (Andrew Cranson) Date: Mon Aug 1 14:21:24 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <9e7db911050801111313b524bd@mail.gmail.com> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> <9e7db911050801111313b524bd@mail.gmail.com> Message-ID: <20050801192713.lk9wwmlt8li8kso4@webmail.transnexis.com> > Some OS repackagers break Ruby. Debian used to be the worst culprit, > but you'll want to make sure you have zlib and ruby-zlib (or something > like that) installed, as these *are* parts of core Ruby but some folks > don't see fit to install them with the core Ruby language. > > -austin Thank you for responding Austin. I compiled and installed ruby, fcgi and mod_fastcgi from source rather than using RPM's. I have zlib RPM installed. Would I need to install ruby-zlib manually from source, or should it be part of the ruby installation? Thanks, From chad at chadfowler.com Mon Aug 1 16:55:43 2005 From: chad at chadfowler.com (chad@chadfowler.com) Date: Mon Aug 1 15:43:03 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <20050801192713.lk9wwmlt8li8kso4@webmail.transnexis.com> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> <9e7db911050801111313b524bd@mail.gmail.com> <20050801192713.lk9wwmlt8li8kso4@webmail.transnexis.com> Message-ID: <50103.216.77.69.67.1122929743.squirrel@216.77.69.67> >> Some OS repackagers break Ruby. Debian used to be the worst culprit, >> but you'll want to make sure you have zlib and ruby-zlib (or something >> like that) installed, as these *are* parts of core Ruby but some folks >> don't see fit to install them with the core Ruby language. >> >> -austin > > Thank you for responding Austin. I compiled and installed ruby, fcgi and > mod_fastcgi from source rather than using RPM's. I have zlib RPM > installed. > Would I need to install ruby-zlib manually from source, or should it be > part of > the ruby installation? > > Thanks, > > __ Hi! On Redhat, you probably need to have something like zlib-devel or the Ruby compile wouldn't end up being able to compile the zlib module. You might want to check the compile log to see what happened during the configure. My bet is that you don't have the necessary -devel packages for RHES, though I'm far from being a Redhat expert. On a Fedora system I have access to, I have this: zlib-devel-1.2.0.7-2 (rpm -qa|grep zlib) Chad From cranky at transnexis.com Mon Aug 1 17:28:18 2005 From: cranky at transnexis.com (Andrew Cranson) Date: Mon Aug 1 17:22:26 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <50103.216.77.69.67.1122929743.squirrel@216.77.69.67> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> <9e7db911050801111313b524bd@mail.gmail.com> <20050801192713.lk9wwmlt8li8kso4@webmail.transnexis.com> <50103.216.77.69.67.1122929743.squirrel@216.77.69.67> Message-ID: <20050801222818.zlq66w2tuim8owck@webmail.transnexis.com> >> Thank you for responding Austin. I compiled and installed ruby, fcgi and >> mod_fastcgi from source rather than using RPM's. I have zlib RPM >> installed. >> Would I need to install ruby-zlib manually from source, or should it be >> part of >> the ruby installation? >> >> Thanks, >> >> __ > > Hi! On Redhat, you probably need to have something like zlib-devel or the > Ruby compile > wouldn't end up being able to compile the zlib module. You might want to > check the compile log > to see what happened during the configure. My bet is that you don't have > the necessary -devel packages for RHES, though I'm far from being a Redhat > expert. > > On a Fedora system I have access to, I have this: zlib-devel-1.2.0.7-2 Hi, Thanks for the reply. I also had zlib-devel RPM installed and located zlib.h in: /usr/local/src/gcc-3.3/zlib/zlib.h RPM's: zlib-devel-1.1.4-8.1 zlib-1.1.4-8.1 gcc-3.2.3-49 libgcc-ssa-3.5ssa-0.20030801.48 libgcc-3.2.3-49 From Source: fcgi-2.4.0 mod_fastcgi-2.4.2 ruby-1.8.2 rubygems-0.8.11 (also tried 0.8.10) Did you compile ruby, fcgi and mod_fastcgi from source when installing on the Fedora system? I can't see anything suspect when configuring. I've attached a copy of the ./configure output of ruby-1.8.2. I appreciate the help. Thanks, Andrew -------------- next part -------------- checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking whether gcc needs -traditional... no checking whether the linker is GNU ld... yes checking whether gcc -E accepts -o... yes checking for bison... no checking for byacc... no checking for ranlib... ranlib checking for ar... ar checking whether ln -s works... yes checking whether make sets $(MAKE)... yes checking for AIX... no checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for _LARGE_FILES value needed for large files... no checking for long long... yes checking for off_t... yes checking for int... yes checking size of int... 4 checking for short... yes checking size of short... 2 checking for long... yes checking size of long... 4 checking for long long... (cached) yes checking size of long long... 8 checking for __int64... no checking size of __int64... 0 checking for off_t... (cached) yes checking size of off_t... 8 checking for void*... yes checking size of void*... 4 checking for float... yes checking size of float... 4 checking for double... yes checking size of double... 8 checking for time_t... yes checking size of time_t... 4 checking for prototypes... yes checking token paste string... ansi checking for variable length prototypes and stdarg.h... yes checking for noreturn... x __attribute__ ((noreturn)) checking whether sys_nerr is declared... yes checking for crypt in -lcrypt... yes checking for dlopen in -ldl... yes checking for shl_load in -ldld... no checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for ANSI C header files... (cached) yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking sys/file.h usability... yes checking sys/file.h presence... yes checking for sys/file.h... yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking sys/fcntl.h usability... yes checking sys/fcntl.h presence... yes checking for sys/fcntl.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/times.h usability... yes checking sys/times.h presence... yes checking for sys/times.h... yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking syscall.h usability... yes checking syscall.h presence... yes checking for syscall.h... yes checking pwd.h usability... yes checking pwd.h presence... yes checking for pwd.h... yes checking grp.h usability... yes checking grp.h presence... yes checking for grp.h... yes checking a.out.h usability... yes checking a.out.h presence... yes checking for a.out.h... yes checking utime.h usability... yes checking utime.h presence... yes checking for utime.h... yes checking for memory.h... (cached) yes checking direct.h usability... no checking direct.h presence... no checking for direct.h... no checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking sys/mkdev.h usability... no checking sys/mkdev.h presence... no checking for sys/mkdev.h... no checking sys/utime.h usability... no checking sys/utime.h presence... no checking for sys/utime.h... no checking netinet/in_systm.h usability... yes checking netinet/in_systm.h presence... yes checking for netinet/in_systm.h... yes checking float.h usability... yes checking float.h presence... yes checking for float.h... yes checking ieeefp.h usability... no checking ieeefp.h presence... no checking for ieeefp.h... no checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking ucontext.h usability... yes checking ucontext.h presence... yes checking for ucontext.h... yes checking intrinsics.h usability... no checking intrinsics.h presence... no checking for intrinsics.h... no checking for uid_t in sys/types.h... yes checking for size_t... yes checking for struct stat.st_blksize... yes checking for struct stat.st_blocks... yes checking for struct stat.st_rdev... yes checking type of array argument to getgroups... gid_t checking return type of signal handlers... void checking for working alloca.h... yes checking for alloca... yes checking for working memcmp... yes checking for _LARGEFILE_SOURCE value needed for large files... 1 checking for fseeko... yes checking for ftello... yes checking for dup2... yes checking for memmove... yes checking for mkdir... yes checking for strcasecmp... yes checking for strncasecmp... yes checking for strerror... yes checking for strftime... yes checking for strchr... yes checking for strstr... yes checking for strtoul... yes checking for crypt... yes checking for flock... yes checking for vsnprintf... yes checking for isnan... yes checking for finite... yes checking for isinf... yes checking for hypot... yes checking for acosh... yes checking for erf... yes checking for fmod... yes checking for killpg... yes checking for wait4... yes checking for waitpid... yes checking for syscall... yes checking for chroot... yes checking for fsync... yes checking for getcwd... yes checking for truncate... yes checking for chsize... no checking for times... yes checking for utimes... yes checking for fcntl... yes checking for lockf... yes checking for lstat... yes checking for symlink... yes checking for readlink... yes checking for setitimer... yes checking for setruid... no checking for seteuid... yes checking for setreuid... yes checking for setresuid... yes checking for setproctitle... no checking for setrgid... no checking for setegid... yes checking for setregid... yes checking for setresgid... yes checking for issetugid... no checking for pause... yes checking for lchown... yes checking for lchmod... no checking for getpgrp... yes checking for setpgrp... yes checking for getpgid... yes checking for setpgid... yes checking for initgroups... yes checking for getgroups... yes checking for setgroups... yes checking for getpriority... yes checking for getrlimit... yes checking for dlopen... yes checking for sigprocmask... yes checking for sigaction... yes checking for _setjmp... yes checking for setsid... yes checking for telldir... yes checking for seekdir... yes checking for fchmod... yes checking for mktime... yes checking for timegm... yes checking for cosh... yes checking for sinh... yes checking for tanh... yes checking for setuid... yes checking for setgid... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for struct tm.tm_zone... yes checking for struct tm.tm_gmtoff... yes checking for external int daylight... yes checking for negative time_t for gmtime(3)... yes checking whether getpgrp requires zero arguments... yes checking whether setpgrp takes no argument... yes checking whether byte ordering is bigendian... no checking for an ANSI C-conforming const... yes checking whether char is unsigned... no checking for inline... inline checking for working volatile... yes checking whether right shift preserve sign bit... yes checking read count field in FILE structures... not found(OK if using GNU libc) checking read buffer ptr field in FILE structures... _IO_read_ptr checking read buffer end field in FILE structures... _IO_read_end checking whether need to seek between R/W... no checking whether st_ino is huge... yes checking stack growing direction... (cached) -1 checking whether ELF binaries are produced... yes checking whether OS depend dynamic link works... yes checking for nroff... /usr/bin/nroff config.h unchanged configure: creating ./config.status config.status: creating Makefile From colin.mailinglist at gmail.com Tue Aug 2 19:45:01 2005 From: colin.mailinglist at gmail.com (Colin Fleming) Date: Tue Aug 2 19:39:10 2005 Subject: [Rubygems-developers] Gem Cache Message-ID: <7c651211050802164548c869e@mail.gmail.com> Hi all, I'm trying to get a slightly odd Gems setup as part of making a self-contained Rails environment. Specifically, I'd like to control where the cache goes, but it seems to be impossible. The docs say that the GEMCACHE env var should be used to specify where the "cache file" goes if the standard cache file is unwriteable. Is this in fact supposed to read "cache dir"? If not, what is the cache file? In any case, if I try making the cache dir unwriteable right after install I just get an error: $chmod -w env/lib/ruby/gems/1.8/cache $gem install rails --include-dependencies Attempting remote installation of 'rails' ERROR: While executing gem ... (Errno::EACCES) Permission denied - /home/colin/dev/ruby/sandbox/env/lib/ruby/gems/1.8/cache/rake-0.5.4.gem and a quick look at the code shows that the path seems to be hard coded: def install(gem_name, version_requirement = "> 0.0.0", force=false, install_dir=Gem.dir, install_stub=true) ...... cache_dir = File.join(install_dir, "cache") And looking at the install code, it passes either Gem.dir or the -i parameter from the command line to install_dir. So it seems to be impossible to change the cache location independently of the install location, is this correct? setup.rb also seems to ignore the --rubypath option (i.e. I can't get it to change the shebang line). In general getting Gems to do abnormal things has been very frustrating, and much harder than IMO it should be. If I get a bit of time and these are really bugs I'll try and patch them. Cheers, Colin From cranky at transnexis.com Wed Aug 3 11:33:36 2005 From: cranky at transnexis.com (Andrew Cranson) Date: Wed Aug 3 11:27:42 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <50103.216.77.69.67.1122929743.squirrel@216.77.69.67> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> <9e7db911050801111313b524bd@mail.gmail.com> <20050801192713.lk9wwmlt8li8kso4@webmail.transnexis.com> <50103.216.77.69.67.1122929743.squirrel@216.77.69.67> Message-ID: <20050803163336.txwfvfgvzaos0k8g@webmail.transnexis.com> Hi, I'm unfortunately still having no luck. Any ideas would be very much appreciated. Would it be possible to perhaps forward a copy of your Fedora ./configure output Austin so I can see if there are any differences? Thanks. ----- Message from chad@chadfowler.com --------- Date: Mon, 1 Aug 2005 16:55:43 -0400 (EDT) From: chad@chadfowler.com Reply-To: rubygems-developers@rubyforge.org Subject: Re: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib To: rubygems-developers@rubyforge.org >>> Some OS repackagers break Ruby. Debian used to be the worst culprit, >>> but you'll want to make sure you have zlib and ruby-zlib (or something >>> like that) installed, as these *are* parts of core Ruby but some folks >>> don't see fit to install them with the core Ruby language. >>> >>> -austin >> >> Thank you for responding Austin. I compiled and installed ruby, fcgi and >> mod_fastcgi from source rather than using RPM's. I have zlib RPM >> installed. >> Would I need to install ruby-zlib manually from source, or should it be >> part of >> the ruby installation? >> >> Thanks, >> >> __ > > Hi! On Redhat, you probably need to have something like zlib-devel or the > Ruby compile > wouldn't end up being able to compile the zlib module. You might want to > check the compile log > to see what happened during the configure. My bet is that you don't have > the necessary -devel packages for RHES, though I'm far from being a Redhat > expert. > > On a Fedora system I have access to, I have this: zlib-devel-1.2.0.7-2 > > (rpm -qa|grep zlib) > > Chad > > _______________________________________________ > Rubygems-developers mailing list > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > ----- End message from chad@chadfowler.com ----- From halostatue at gmail.com Wed Aug 3 14:23:28 2005 From: halostatue at gmail.com (Austin Ziegler) Date: Wed Aug 3 14:17:36 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <20050803163336.txwfvfgvzaos0k8g@webmail.transnexis.com> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> <9e7db911050801111313b524bd@mail.gmail.com> <20050801192713.lk9wwmlt8li8kso4@webmail.transnexis.com> <50103.216.77.69.67.1122929743.squirrel@216.77.69.67> <20050803163336.txwfvfgvzaos0k8g@webmail.transnexis.com> Message-ID: <9e7db91105080311234fadb4c@mail.gmail.com> On 8/3/05, Andrew Cranson wrote: > Hi, > > I'm unfortunately still having no luck. Any ideas would be very much > appreciated. Would it be possible to perhaps forward a copy of your Fedora > ./configure output Austin so I can see if there are any differences? Sorry; I don't use Fedora. I was basing my response on things that I've seen in the past. -austin -- Austin Ziegler * halostatue@gmail.com * Alternate: austin@halostatue.ca From cranky at transnexis.com Wed Aug 3 14:28:55 2005 From: cranky at transnexis.com (Andrew Cranson) Date: Wed Aug 3 14:23:01 2005 Subject: [Rubygems-developers] /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': No such file to load -- zlib In-Reply-To: <9e7db91105080311234fadb4c@mail.gmail.com> References: <20050801155509.q5j9gadxsiog4ks0@webmail.transnexis.com> <20050801155810.6sx0qs1jwn0g8kgw@webmail.transnexis.com> <9e7db911050801111313b524bd@mail.gmail.com> <20050801192713.lk9wwmlt8li8kso4@webmail.transnexis.com> <50103.216.77.69.67.1122929743.squirrel@216.77.69.67> <20050803163336.txwfvfgvzaos0k8g@webmail.transnexis.com> <9e7db91105080311234fadb4c@mail.gmail.com> Message-ID: <20050803192855.jhta1gh94288k80o@webmail.transnexis.com> Hi Austin, Thanks for your help, I've sorted it now by installing some additional packages: Glide3 Glide3-devel XFree86-Mesa-libGL XFree86-devel XFree86-libs XFree86-libs-data I'm short on time so didn't narrow it down any further, but one of the above allowed me to achieve the desired outcome. Thanks again, Andrew From tilman at code-monkey.de Fri Aug 12 09:58:12 2005 From: tilman at code-monkey.de (Tilman Sauerbeck) Date: Fri Aug 12 09:52:05 2005 Subject: [Rubygems-developers] [PATCH] Support extensions built with rake Message-ID: <20050812135812.GA5828@code-monkey.de> Hi, here's a patch that adds support for gems that use Rake to build extensions. It's assumed that the default rake target will build the extension(s), and that the "install" target will install them. RUBYARCHDIR and RUBYLIBDIR are overridden the same way as it's done for extconf.rb-based extensions. Also, the "clean" target will now be invoked for both extconf.rb-based extensions and for rake-based ones - I don't see why *.o should be kept around :) The patch is probably flawed in several ways, but I hope it's good enough to either merge it or pick it up and improve it until it's good to go ;) Regards, Tilman -- learn to quote: http://www.netmeister.org/news/learn2quote.html -------------- next part -------------- diff -aur rubygems-0.8.11.orig/lib/rubygems/installer.rb rubygems-0.8.11/lib/rubygems/installer.rb --- rubygems-0.8.11.orig/lib/rubygems/installer.rb 2005-06-12 23:33:19.000000000 +0200 +++ rubygems-0.8.11/lib/rubygems/installer.rb 2005-08-11 22:19:32.000000000 +0200 @@ -284,29 +284,31 @@ say "Building native extensions. This could take a while..." start_dir = Dir.pwd dest_path = File.join(directory, spec.require_paths[0]) + spec.extensions.each do |extension| - Dir.chdir File.join(directory, File.dirname(extension)) - results = ["#{Gem.ruby} #{File.basename(extension)} #{ARGV.join(" ")}"] - results << `#{Gem.ruby} #{File.basename(extension)} #{ARGV.join(" ")}` - if File.exist?('Makefile') - mf = File.read('Makefile') - mf = mf.gsub(/^RUBYARCHDIR\s*=\s*\$.*/, "RUBYARCHDIR = #{dest_path}") - mf = mf.gsub(/^RUBYLIBDIR\s*=\s*\$.*/, "RUBYLIBDIR = #{dest_path}") - File.open('Makefile', 'wb') {|f| f.print mf} - make_program = ENV['make'] - unless make_program - make_program = (/mswin/ =~ RUBY_PLATFORM) ? 'nmake' : 'make' - end - results << "#{make_program}" - results << `#{make_program}` - results << "#{make_program} install" - results << `#{make_program} install` - say results.join("\n") + if extension.match(/extconf/) + builder = ExtExtConfBuilder + elsif extension.match(/rakefile/i) + builder = ExtRakeBuilder else - File.open(File.join(Dir.pwd, 'gem_make.out'), 'wb') {|f| f.puts results.join("\n")} - raise "ERROR: Failed to build gem native extension.\nGem files will remain installed in #{directory} for inspection.\n #{results.join('\n')}\n\nResults logged to #{File.join(Dir.pwd, 'gem_make.out')}" + builder = nil + results = ["No builder for extension '#{extension}'"] + end + + begin + err = false + Dir.chdir File.join(directory, File.dirname(extension)) + results = builder.build(extension, directory, dest_path) + rescue + err = true end + + say results.join("\n") File.open('gem_make.out', 'wb') {|f| f.puts results.join("\n")} + + if err + raise "ERROR: Failed to build gem native extension.\nGem files will remain installed in #{directory} for inspection.\n #{results.join('\n')}\n\nResults logged to #{File.join(Dir.pwd, 'gem_make.out')}" + end end Dir.chdir start_dir end @@ -535,4 +537,40 @@ end # class Uninstaller + class ExtExtConfBuilder + def ExtExtConfBuilder.build(extension, directory, dest_path) + results = ["#{Gem.ruby} #{File.basename(extension)} #{ARGV.join(" ")}"] + results << `#{Gem.ruby} #{File.basename(extension)} #{ARGV.join(" ")}` + + raise unless File.exist?('Makefile') + mf = File.read('Makefile') + mf = mf.gsub(/^RUBYARCHDIR\s*=\s*\$.*/, "RUBYARCHDIR = #{dest_path}") + mf = mf.gsub(/^RUBYLIBDIR\s*=\s*\$.*/, "RUBYLIBDIR = #{dest_path}") + File.open('Makefile', 'wb') {|f| f.print mf} + + make_program = ENV['make'] + unless make_program + make_program = (/mswin/ =~ RUBY_PLATFORM) ? 'nmake' : 'make' + end + + ['', 'install', 'clean'].each do |target| + results << "#{make program} #{target}".strip + results << `#{make program} #{target}` + end + end + end + + class ExtRakeBuilder + def ExtRakeBuilder.build(ext, directory, dest_path) + make_program = ENV['rake'] || 'rake' + make_program += " RUBYARCHDIR=#{dest_path} RUBYLIBDIR=#{dest_path}" + + results = [] + + ['', 'install', 'clean'].each do |target| + results << "#{make program} #{target}".strip + results << `#{make program} #{target}` + end + end + end end # module Gem From chad at chadfowler.com Mon Aug 15 20:49:27 2005 From: chad at chadfowler.com (Chad Fowler) Date: Mon Aug 15 20:43:17 2005 Subject: [Rubygems-developers] [PATCH] Support extensions built with rake In-Reply-To: <20050812135812.GA5828@code-monkey.de> References: <20050812135812.GA5828@code-monkey.de> Message-ID: <3FF6741F-6FD5-4B26-B0E6-622CF62F772E@chadfowler.com> On 12-Aug-05, at 9:58 AM, Tilman Sauerbeck wrote: > Thanks, Tilman! Do you have an extension published that we could try this out with? Thanks, Chad From tilman at code-monkey.de Tue Aug 16 12:30:27 2005 From: tilman at code-monkey.de (Tilman Sauerbeck) Date: Tue Aug 16 12:24:18 2005 Subject: [Rubygems-developers] [PATCH] Support extensions built with rake In-Reply-To: <3FF6741F-6FD5-4B26-B0E6-622CF62F772E@chadfowler.com> References: <20050812135812.GA5828@code-monkey.de> <3FF6741F-6FD5-4B26-B0E6-622CF62F772E@chadfowler.com> Message-ID: <20050816183027.62f8a8ee.tilman@code-monkey.de> On Mon, 15 Aug 2005 20:49:27 -0400 Chad Fowler wrote: Hi Chad, > On 12-Aug-05, at 9:58 AM, Tilman Sauerbeck wrote: > > > > > Thanks, Tilman! Do you have an extension published that we could try > this out with? http://code-monkey.de/files/ruby-eet-0.1.3.gem That's the first gem I ever built, so if you find anything weird besides the extension stuff, it's probably my fault ;) Regards, Tilman -- learn to quote: http://www.netmeister.org/news/learn2quote.html From lyle.johnson at gmail.com Thu Aug 18 11:18:06 2005 From: lyle.johnson at gmail.com (Lyle Johnson) Date: Thu Aug 18 11:11:45 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? Message-ID: I'm about to make the first release of FXRuby 1.4, but would like to somehow mark it as an "alpha" release. I'm wondering if there's some way to avoid calling it fxruby-1.4.0.gem (or whatever) which might lead people to thinking it's a stable release. Are there any established patterns for how people do this, or should I just punt and call the first release 1.4.0 and be done with it? From jim at weirichhouse.org Thu Aug 18 12:55:10 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Thu Aug 18 12:48:50 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? In-Reply-To: References: Message-ID: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> Lyle Johnson said: > I'm about to make the first release of FXRuby 1.4, but would like to > somehow mark it as an "alpha" release. I'm wondering if there's some > way to avoid calling it fxruby-1.4.0.gem (or whatever) which might > lead people to thinking it's a stable release. Are there any > established patterns for how people do this, or should I just punt and > call the first release 1.4.0 and be done with it? RubyGems versions are all numeric by design, so there is no way to append an "alpha" or "beta" designation. I tend to use 3 digit versions for official releases and 4 digit versions for releases between official releases. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From lyle.johnson at gmail.com Thu Aug 18 13:50:21 2005 From: lyle.johnson at gmail.com (Lyle Johnson) Date: Thu Aug 18 13:44:03 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? In-Reply-To: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> References: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> Message-ID: On 8/18/05, Jim Weirich wrote: > RubyGems versions are all numeric by design, so there is no way to append > an "alpha" or "beta" designation. I tend to use 3 digit versions for > official releases and 4 digit versions for releases between official > releases. For some reason, I didn't realize that four-digit version numbers were allowed. Are there any examples of this in the wild? The RubyGems documentation (at docs.rubygems.org) doesn't appear to have any examples. When you're doing an update of gems using this numbering scheme, is a gem with version number "1.4.0.1" considered newer than a gem with version number "1.4.0"? How does the comparison work? From jim at weirichhouse.org Thu Aug 18 14:45:16 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Thu Aug 18 14:38:55 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? In-Reply-To: References: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> Message-ID: <37657.192.223.163.6.1124390716.squirrel@weirichhouse.org> Lyle Johnson said: > On 8/18/05, Jim Weirich wrote: > >> RubyGems versions are all numeric by design, so there is no way to >> append >> an "alpha" or "beta" designation. I tend to use 3 digit versions for >> official releases and 4 digit versions for releases between official >> releases. > > For some reason, I didn't realize that four-digit version numbers were > allowed. Are there any examples of this in the wild? The RubyGems > documentation (at docs.rubygems.org) doesn't appear to have any > examples. When you're doing an update of gems using this numbering > scheme, is a gem with version number "1.4.0.1" considered newer than a > gem with version number "1.4.0"? How does the comparison work? Hmmm ... you are right. The documentation never explicitly says three part versions, although that is the recommended scheme and most of the examples use three part versions. However, a version may have as many parts as you want, provided each part is numeric and the parts are separated by a period. Look at http://onestepback.org/betagems/gems for a number of my beta gems with four digit versions. I don't generally release the four part betas on rubyforge, but I do often upload them to http://onestepback.org/betagems for limited release. When comparing versions with a different number of parts, the shorter version is extended on the right with zeros. -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From lyle.johnson at gmail.com Thu Aug 18 15:19:25 2005 From: lyle.johnson at gmail.com (Lyle Johnson) Date: Thu Aug 18 15:13:04 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? In-Reply-To: <37657.192.223.163.6.1124390716.squirrel@weirichhouse.org> References: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> <37657.192.223.163.6.1124390716.squirrel@weirichhouse.org> Message-ID: On 8/18/05, Jim Weirich wrote: > Hmmm ... you are right. The documentation never explicitly says three > part versions, although that is the recommended scheme and most of the > examples use three part versions. However, a version may have as many > parts as you want, provided each part is numeric and the parts are > separated by a period. OK. > Look at http://onestepback.org/betagems/gems for a number of my beta gems > with four digit versions. I don't generally release the four part betas > on rubyforge, but I do often upload them to > http://onestepback.org/betagems for limited release. > > When comparing versions with a different number of parts, the shorter > version is extended on the right with zeros. Thanks for the examples, I get it now! From scholz at scriptolutions.com Thu Aug 18 20:58:52 2005 From: scholz at scriptolutions.com (Lothar Scholz) Date: Thu Aug 18 20:52:48 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? In-Reply-To: References: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> Message-ID: <1959548796.20050819075852@scriptolutions.com> Hello Lyle, Friday, August 19, 2005, 12:50:21 AM, you wrote: LJ> On 8/18/05, Jim Weirich wrote: >> RubyGems versions are all numeric by design, so there is no way to append >> an "alpha" or "beta" designation. I tend to use 3 digit versions for >> official releases and 4 digit versions for releases between official >> releases. LJ> For some reason, I didn't realize that four-digit version numbers were LJ> allowed. Are there any examples of this in the wild? The RubyGems LJ> documentation (at docs.rubygems.org) doesn't appear to have any LJ> examples. When you're doing an update of gems using this numbering LJ> scheme, is a gem with version number "1.4.0.1" considered newer than a LJ> gem with version number "1.4.0"? How does the comparison work? What about using a 2 digit schema for normal and 3 digit for alpha. There are already a few out there that do just this but i've never seen a 4 digit version. -- Best regards, Lothar Scholz mailto:scholz@scriptolutions.com From jim.weirich at gmail.com Sat Aug 20 09:28:07 2005 From: jim.weirich at gmail.com (Jim Weirich) Date: Sat Aug 20 09:21:46 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? In-Reply-To: <1959548796.20050819075852@scriptolutions.com> References: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> <1959548796.20050819075852@scriptolutions.com> Message-ID: On 8/18/05, Lothar Scholz wrote: > What about using a 2 digit schema for normal and 3 digit for alpha. > There are already a few out there that do just this but i've never > seen a 4 digit version. Ahhh ... the voice of reason. This is probably a good idea. The three digit variety probably is too fined grained for most people anyways. -- -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From ryand-ruby at zenspider.com Wed Aug 24 02:10:17 2005 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Wed Aug 24 02:03:53 2005 Subject: [Rubygems-developers] Advice on version numbers for alpha releases? In-Reply-To: <1959548796.20050819075852@scriptolutions.com> References: <50755.192.223.163.6.1124384110.squirrel@weirichhouse.org> <1959548796.20050819075852@scriptolutions.com> Message-ID: <11E5EEA4-FBB1-47B7-9D3D-A51F45C51895@zenspider.com> On Aug 18, 2005, at 5:58 PM, Lothar Scholz wrote: > Hello Lyle, > > Friday, August 19, 2005, 12:50:21 AM, you wrote: > > LJ> On 8/18/05, Jim Weirich wrote: > > >>> RubyGems versions are all numeric by design, so there is no way >>> to append >>> an "alpha" or "beta" designation. I tend to use 3 digit versions >>> for >>> official releases and 4 digit versions for releases between official >>> releases. >>> > > LJ> For some reason, I didn't realize that four-digit version > numbers were > LJ> allowed. Are there any examples of this in the wild? The RubyGems > LJ> documentation (at docs.rubygems.org) doesn't appear to have any > LJ> examples. When you're doing an update of gems using this numbering > LJ> scheme, is a gem with version number "1.4.0.1" considered newer > than a > LJ> gem with version number "1.4.0"? How does the comparison work? > > What about using a 2 digit schema for normal and 3 digit for alpha. > There are already a few out there that do just this but i've never > seen a 4 digit version. 505 % gem list --remote RubyToC *** REMOTE GEMS *** RubyToC (1.0.0.4) Ruby (subset) to C translator. I do /major\.minor\.bug ((alpha|beta) release)?/ (where major, minor, bug, and release all /\d+/) Since I can't do "alpha" or "beta" I have to strip it for the gem version number. From hgs at dmu.ac.uk Thu Aug 25 13:43:54 2005 From: hgs at dmu.ac.uk (Hugh Sasse) Date: Thu Aug 25 19:33:15 2005 Subject: [Rubygems-developers] caught RedHanded :-) Message-ID: An article on RedHanded (Sneaking Ruby through the System), http://redhanded.hobix.com/inspect/theCoastIsClearToVocallyPraiseRubygems.html by _Why has raised a number of comments and questions. Maybe someone more familiar with the internals, etc, would like to enlighten people there? Else, just read it for the praise of Gems. Hugh From chad at chadfowler.com Fri Aug 26 08:25:30 2005 From: chad at chadfowler.com (Chad Fowler) Date: Fri Aug 26 08:18:59 2005 Subject: [Rubygems-developers] caught RedHanded :-) In-Reply-To: References: Message-ID: On 25-Aug-05, at 1:43 PM, Hugh Sasse wrote: > An article on RedHanded (Sneaking Ruby through the System), > http://redhanded.hobix.com/inspect/ > theCoastIsClearToVocallyPraiseRubygems.html > by _Why has raised a number of comments and questions. Maybe > someone more familiar with the internals, etc, would like to > enlighten people there? Else, just read it for the praise of Gems. > > Thanks, Hugh! I've posted some comments. Everyone else is obviously welcome to do the same. Seeya, Chad From tilman at code-monkey.de Tue Aug 30 15:56:20 2005 From: tilman at code-monkey.de (Tilman Sauerbeck) Date: Tue Aug 30 15:49:38 2005 Subject: [Rubygems-developers] [PATCH] Support extensions built with rake In-Reply-To: <3FF6741F-6FD5-4B26-B0E6-622CF62F772E@chadfowler.com> References: <20050812135812.GA5828@code-monkey.de> <3FF6741F-6FD5-4B26-B0E6-622CF62F772E@chadfowler.com> Message-ID: <20050830215620.22432409.tilman@code-monkey.de> On Mon, 15 Aug 2005 20:49:27 -0400 Chad Fowler wrote: > On 12-Aug-05, at 9:58 AM, Tilman Sauerbeck wrote: > > > So, any problems with that patch (I guess so)? Let me know what sucks about it so I can fix it, I'd really like to see that feature hit CVS :) -- learn to quote: http://www.netmeister.org/news/learn2quote.html From chad at chadfowler.com Tue Aug 30 16:30:09 2005 From: chad at chadfowler.com (Chad Fowler) Date: Tue Aug 30 16:23:31 2005 Subject: [Rubygems-developers] [PATCH] Support extensions built with rake In-Reply-To: <20050830215620.22432409.tilman@code-monkey.de> References: <20050812135812.GA5828@code-monkey.de> <3FF6741F-6FD5-4B26-B0E6-622CF62F772E@chadfowler.com> <20050830215620.22432409.tilman@code-monkey.de> Message-ID: On 30-Aug-05, at 3:56 PM, Tilman Sauerbeck wrote: > On Mon, 15 Aug 2005 20:49:27 -0400 Chad Fowler > wrote: > > >> On 12-Aug-05, at 9:58 AM, Tilman Sauerbeck wrote: >> >> >>> >>> > > So, any problems with that patch (I guess so)? > Let me know what sucks about it so I can fix it, I'd really like to > see that feature hit CVS :) Hi! Sorry! I've been super busy at home and let this slip off the radar! Are you able to install your ruby-eet gem using this patch? I get this: $ sudo gem install ruby-eet-0.1.3.gem --backtrace Attempting local installation of 'ruby-eet-0.1.3.gem' Building native extensions. This could take a while... ERROR: Error installing gem ruby-eet-0.1.3.gem[.gem]: undefined method `join' for nil:NilClass "backtrace" isn't showing anything for some reason in my case and I haven't had a chance to debug yet. I wanted to validate that you were able to run this before I spend too much time on it. Thanks, Chad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubygems-developers/attachments/20050830/73a6d290/attachment.htm From tilman at code-monkey.de Tue Aug 30 17:06:21 2005 From: tilman at code-monkey.de (Tilman Sauerbeck) Date: Tue Aug 30 16:59:45 2005 Subject: [Rubygems-developers] [PATCH] Support extensions built with rake In-Reply-To: References: <20050812135812.GA5828@code-monkey.de> <3FF6741F-6FD5-4B26-B0E6-622CF62F772E@chadfowler.com> <20050830215620.22432409.tilman@code-monkey.de> Message-ID: <20050830230621.4fe3add9.tilman@code-monkey.de> On Tue, 30 Aug 2005 16:30:09 -0400 Chad Fowler wrote: > > On 30-Aug-05, at 3:56 PM, Tilman Sauerbeck wrote: > > > On Mon, 15 Aug 2005 20:49:27 -0400 Chad Fowler > > wrote: > > > > > >> On 12-Aug-05, at 9:58 AM, Tilman Sauerbeck wrote: > >> > >> > >>> > >>> > > > > So, any problems with that patch (I guess so)? > > Let me know what sucks about it so I can fix it, I'd really like to > > see that feature hit CVS :) > > Hi! Sorry! I've been super busy at home and let this slip off the > radar! No problem :) > Are you able to install your ruby-eet gem using this patch? I get this: > > $ sudo gem install ruby-eet-0.1.3.gem --backtrace > Attempting local installation of 'ruby-eet-0.1.3.gem' > Building native extensions. This could take a while... > ERROR: Error installing gem ruby-eet-0.1.3.gem[.gem]: undefined > method `join' for nil:NilClass Ugh, I think I attached the wrong diff :O Try this one, I just verified that it's working for me. Regards, Tilman -- learn to quote: http://www.netmeister.org/news/learn2quote.html -------------- next part -------------- A non-text attachment was scrubbed... Name: rubygems-rake_ext2.diff Type: application/octet-stream Size: 4006 bytes Desc: not available Url : http://rubyforge.org/pipermail/rubygems-developers/attachments/20050830/93fda5f2/rubygems-rake_ext2-0001.obj From drbrain at segment7.net Tue Aug 30 22:36:13 2005 From: drbrain at segment7.net (Eric Hodel) Date: Wed Aug 31 13:05:29 2005 Subject: [Rubygems-developers] Where's install.rb? Message-ID: $ pwd /Users/drbrain/Work/cvs/rubygems/rubygems $ rake install (in /Users/drbrain/Work/cvs/rubygems/rubygems) ruby18 install.rb ruby18: No such file or directory -- install.rb (LoadError) rake aborted! Command failed with status (1): [ruby18 install.rb] ./rakefile:283 $ cvs up install.rb $ -- Eric Hodel - drbrain@segment7.net - http://segment7.net FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 From jim at weirichhouse.org Wed Aug 31 14:18:30 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Wed Aug 31 14:11:46 2005 Subject: [Rubygems-developers] Where's install.rb? In-Reply-To: References: Message-ID: <18547.192.223.163.6.1125512310.squirrel@weirichhouse.org> Eric Hodel said: > $ pwd > /Users/drbrain/Work/cvs/rubygems/rubygems > $ rake install > (in /Users/drbrain/Work/cvs/rubygems/rubygems) > ruby18 install.rb > ruby18: No such file or directory -- install.rb (LoadError) > rake aborted! > Command failed with status (1): [ruby18 install.rb] > ./rakefile:283 > $ cvs up install.rb Hmmm ... install.rb has been replaced with setup.rb. Obviously the rake install task wasn't told about the switch :) -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) From jim at weirichhouse.org Wed Aug 31 21:42:15 2005 From: jim at weirichhouse.org (Jim Weirich) Date: Wed Aug 31 21:35:18 2005 Subject: [Rubygems-developers] Where's install.rb? In-Reply-To: <18547.192.223.163.6.1125512310.squirrel@weirichhouse.org> References: <18547.192.223.163.6.1125512310.squirrel@weirichhouse.org> Message-ID: <200508312142.15442.jim@weirichhouse.org> On Wednesday 31 August 2005 02:18 pm, Jim Weirich wrote: > Eric Hodel said: > > $ pwd > > /Users/drbrain/Work/cvs/rubygems/rubygems > > $ rake install > > (in /Users/drbrain/Work/cvs/rubygems/rubygems) > > ruby18 install.rb > > ruby18: No such file or directory -- install.rb (LoadError) > > rake aborted! > > Command failed with status (1): [ruby18 install.rb] > > ./rakefile:283 > > $ cvs up install.rb > > Hmmm ... install.rb has been replaced with setup.rb. Obviously the rake > install task wasn't told about the switch :) Rake has now been informed of the change in install procedures (in CVS). -- -- Jim Weirich jim@weirichhouse.org http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)