rubycocoa-talk

[Rubycocoa-talk] New ways to not install Ruby things.

[Dave h. <eb...@Gr...>]

Well, the Rails installation has finally failed completely. I reached 
the point where Rails would get invoked when the right page was called, 
and I could even get results back, usually, *if* I did not attempt to 
communicate with my database. I couldn't get it to generate a useful 
error message, so I shelved that for a couple days.

Then my entire 'server data partition' (where websites, mail, and 
database files live) was obliterated when my RAID array botched a 
rebuild of a faulty drive on the one day in the past three months when 
I didn't have a backup of the whole thing.

So it's something of a moot point. I am now shopping for a used XServe.

I moved back to my other project, the RubyCocoa task list manager. 
That's been blowing up with bus errors for no obvious reason. Since 
it's clearly a fault in RubyCocoa, Ruby, or OSX, instead of programmer 
error, I've been a bit stymied. Since I now know that my 1.8.2 is the 
November version, I decided to install the December one.

Well, from the command line, I get the new 1.8.2 (darwin7.9.0). But 
XCode can't let go of the older, powerpc-darwin7.5.0 version, and 
continues to fail with a bus error semi-randomly. I have no idea how to 
get it to get a clue; repeated fiddling on my part just upsets it when 
it can't find the older libraries or whatever it's looking for.

I decided to scrap everything and reinstall Ruby from scratch.

In order to be able to tell the difference between the older 1.8.2 and 
the newer 1.8.2, I named the newer version "ruby-1.8.2(12/25/04)".  How 
delightful to discover that "make install" can't handle parentheses. 
Configure didn't bat an eye. Make didn't have a problem. But Make 
Install instantly fails. And if I change the directory name, it still 
fails, since it turns out that ./configure hard-coded its own directory 
into the files it built. So I have to start over from the very 
beginning.

Then I can try installing gems. Then RubyCocoa. Then Rails.

[pause]

Or not. Make has failed.

	compiling iconv
	gcc -fno-common -g -O2 -pipe -fno-common  -I. -I../.. -I../../. 
-I../.././ext/iconv 	-DICONV_INPTR_CAST="(char **)"  -c iconv.c
	iconv.c:1: bad macro argument list
	iconv.c:231: illegal function call, found `inptr'
	cpp-precomp: warning: errors during smart preprocessing, retrying in 
basic mode
	<built-in>:1:1: no macro name given in #define directive
	make[1]: *** [iconv.o] Error 1
	make: *** [all] Error 1

Let's try again....nope, my installation directory is now mysteriously 
corrupted. I must now erase it and download a whole new copy of Ruby.  
I guess I'll try the package that 'discordantus' put together. After I 
finish banging my head against the wall.

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Tim L. <t....@to...>]

On 17/09/2005, at 7:56 AM, Dave howell wrote:


> Let's try again....nope, my installation directory is now  
> mysteriously corrupted. I must now erase it and download a whole  
> new copy of Ruby.  I guess I'll try the package that 'discordantus'  
> put together. After I finish banging my head against the wall.
>

Why not install from darwinports?

Step 1) Install darwinports
Step 2) sudo port install ruby rails rubygems
Step 3) there is no step 3 :)

Rubycocoa and anything else can use the darwinports ruby install just  
fine by adding /opt/local/bin to your path and changing the shebangs  
to '/usr/bin/env ruby'

... oh, and darwinports doesn't clutter your system -- everything  
sits under /opt/local/ so you can try it out w/o fear of nuking your  
default system libraries.

-- tim lucas

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Matt M. <mat...@gm...>]

On 17/09/05, Tim Lucas <t....@to...> wrote:
> On 17/09/2005, at 7:56 AM, Dave howell wrote:
>=20
>=20
> > Let's try again....nope, my installation directory is now
> > mysteriously corrupted. I must now erase it and download a whole
> > new copy of Ruby.  I guess I'll try the package that 'discordantus'
> > put together. After I finish banging my head against the wall.
> >
>=20
> Why not install from darwinports?
>=20

What Tim said.

M

--=20
Matt Mower :: http://matt.blogs.it/

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave H. <gr...@gr...>]

With the announcement of 0.4.2 I thought I might be able to move 
forward on some Ruby projects.

Go to web site. Go to download page. Download Panther installer. 
Install. Watch Ruby fail to compile.

The download page says "Before downloading, you may want to read the 
Release Notes and ChangeLog." There do not appear to be any "Release 
Notes" on that page, nor any obvious links to same.


If I instead do

Go to web site. Follow link to "main page." Follow link to "Getting 
RubyCocoa", then I see a notice that the binary distributions are for 
ruby 1.6.8. I'm using ruby 1.8.2. I'll just guess that's why it can't 
compile.

Yes? No?

I guess I'll try compiling from source . . . .

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Jonathan P. <jp...@dc...>]

On 8 Dec 2005, at 1:50, Dave Howell wrote:

> Go to web site. Go to download page. Download Panther installer.  
> Install. Watch Ruby fail to compile.

Please give precise details of the failure you experienced. What  
steps did you take, and what results did you get? "fail to compile"  
isn't enough information to help diagnose the problem.

What version of OS X are you using? Have you done anything to the  
standard Ruby installation (e.g., removed bits of it)?

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave H. <gr...@gr...>]

On Dec 8, 2005, at 0:36, Jonathan Paisley wrote:

> On 8 Dec 2005, at 1:50, Dave Howell wrote:
>
>> Go to web site. Go to download page. Download Panther installer. 
>> Install. Watch Ruby fail to compile.
>
> Please give precise details of the failure you experienced. What steps 
> did you take, and what results did you get? "fail to compile" isn't 
> enough information to help diagnose the problem.
>
> What version of OS X are you using? Have you done anything to the 
> standard Ruby installation (e.g., removed bits of it)?

As my earlier messages mentioned, I'm using Panther (as it happens, 
it's the current release, so it's 10.3.9), the error message is "can't 
open library: /usr/lib/libruby.1.dylib  (No such file or directory, 
errno = 2)", I'm using 1.8.2, which means I can't be using the 
"standard Ruby installation," and indeed, if I hadn't completely 
obliterated it from my OS (so, yes, I've removed bits. All the bits. 
Every last bit I could find), it would be happily compiling the *wrong* 
version of Ruby into my code and making my life incredibly miserable.

What steps did I take? I hit "Build and Run." For all of my current 
projects, even ones that have not changed at all since they last 
compiled successfully, I now get the same error message.

The question is: What did the pre-built Panther Install package screw 
up that the "ruby install.rb" script wasn't smart enough to fix? 
"libruby.1.dylib" is installed into /usr/local/lib. How do I force 
XCode to look where the library really is, and why didn't RubyCocoa's 
"install.rb" file set it up correctly in the first place? This was all 
working with RubyCocoa 0.4.1. Now it's not.

I could reset the files by restoring from my backups, but I rather 
doubt that the file containing the corrupted path is in the /usr tree, 
and I can't roll back my entire hard drive two days.

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Jonathan P. <jp...@dc...>]

> As my earlier messages mentioned, I'm using Panther (as it happens,  
> it's the current release, so it's 10.3.9), the error message is  
> "can't open library:

My apologies. I hadn't realised that there were now separate dmg  
distributions for Panther and Tiger.

> /usr/lib/libruby.1.dylib  (No such file or directory, errno = 2)",  
> I'm using 1.8.2, which means I can't be using the "standard Ruby  
> installation," and indeed, if I hadn't completely obliterated it  
> from my OS (so, yes, I've removed bits. All the bits. Every last  
> bit I could find), it would be happily compiling the *wrong*  
> version of Ruby into my code and making my life incredibly miserable.

Can you confirm that the ruby installation picked up from the command  
line is your self-installed 1.8.2?

    which ruby
    ruby -v

> What steps did I take? I hit "Build and Run." For all of my current  
> projects, even ones that have not changed at all since they last  
> compiled successfully, I now get the same error message.

Can you check that your self-compiled RubyCocoa has definitely been  
installed in /Library/Frameworks? It sounds like perhaps the one from  
the dmg is still there.

Try removing /Library/Frameworks/RubyCocoa.framework altogether and  
rerunning the source install.

> The question is: What did the pre-built Panther Install package  
> screw up that the "ruby install.rb" script wasn't smart enough to  
> fix? "libruby.1.dylib" is installed into /usr/local/lib. How do I  
> force XCode to look where the library really is, and why didn't  
> RubyCocoa's "install.rb" file set it up correctly in the first  
> place? This was all working with RubyCocoa 0.4.1. Now it's not.

The reference to /usr/lib/libruby.1.dylib is probably coming from the  
RubyCocoa framework. You can check with the 'otool -L' command, which  
shows library dependencies (the example below is for the 0.4.2  
Panther dmg):

   otool -L /Library/Frameworks/RubyCocoa.framework/RubyCocoa
../RubyCocoa:
	@executable_path/../Frameworks/RubyCocoa.framework/Versions/A/ 
RubyCocoa (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa  
(compatibility version 1.0.0, current version 9.0.0)
	/usr/lib/libruby.1.dylib (compatibility version 1.6.0, current  
version 1.6.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current  
version 71.1.4)

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave H. <gr...@gr...>]

On Dec 8, 2005, at 4:00, Jonathan Paisley wrote:

>
> Try removing /Library/Frameworks/RubyCocoa.framework altogether and 
> rerunning the source install.

sudo rm  -R /Library/Frameworks/RubyCocoa.framework
sudo ruby install.rb install

Attempt to run "test"
"can't open library: /usr/lib/libruby.1.dylib  (No such file or 
directory, errno = 2)"

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave B. <dav...@3d...>]

On 8 Dec 2005, at 01:50, Dave Howell wrote:

> With the announcement of 0.4.2 I thought I might be able to move  
> forward on some Ruby projects.
>
> Go to web site. Go to download page. Download Panther installer.  
> Install. Watch Ruby fail to compile.
>

I thought 0.4.2 included access to tiger only functionality (i.e.  
core data).  Don't know what it will do when it cannot find this.
May have nothing to do with your problem...

Dave.

> The download page says "Before downloading, you may want to read  
> the Release Notes and ChangeLog." There do not appear to be any  
> "Release Notes" on that page, nor any obvious links to same.
>
>
> If I instead do
>
> Go to web site. Follow link to "main page." Follow link to "Getting  
> RubyCocoa", then I see a notice that the binary distributions are  
> for ruby 1.6.8. I'm using ruby 1.8.2. I'll just guess that's why it  
> can't compile.
>
> Yes? No?
>
> I guess I'll try compiling from source . . . .
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave H. <gr...@gr...>]

On Dec 7, 2005, at 17:50, Dave Howell wrote:

> I guess I'll try compiling from source . . . .

"ruby install.rb config" failed. It can't handles spaces in the path.

I guess I'll have to relocate it to some directory that doesn't have 
any spaces in its path . . .





This is why I didn't install RubyCocoa 0.4.2 as soon as it was 
released; I don't recall ever having installed *any* Ruby-related 
software without having to to deal with multiple problems during the 
install. Sigh.

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave H. <gr...@gr...>]

On Dec 7, 2005, at 17:58, Dave Howell wrote:

> "ruby install.rb config" failed. It can't handles spaces in the path.
>
> I guess I'll have to relocate it to some directory that doesn't have 
> any spaces in its path . . .

Got it installed.

Still can't run a Ruby app from XCode, though:

can't open library: /usr/lib/libruby.1.dylib  (No such file or 
directory, errno = 2)

Well, no kidding. That's because it's in /usr/local/lib.

Quit and restart XCode. Nope.

Log out and in. Nope.

Reboot. Nope.



OK, so what did the Panther Install package screw up that the "ruby 
install.rb" script wasn't smart enough to fix?

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave B. <dav...@3d...>]

On 8 Dec 2005, at 02:18, Dave Howell wrote:

>
> On Dec 7, 2005, at 17:58, Dave Howell wrote:
>
>> "ruby install.rb config" failed. It can't handles spaces in the path.
>>
>> I guess I'll have to relocate it to some directory that doesn't  
>> have any spaces in its path . . .
>
> Got it installed.
>
> Still can't run a Ruby app from XCode, though:
>
> can't open library: /usr/lib/libruby.1.dylib  (No such file or  
> directory, errno = 2)
>
> Well, no kidding. That's because it's in /usr/local/lib.
>
> Quit and restart XCode. Nope.
>
> Log out and in. Nope.
>
> Reboot. Nope.


Have you tried running from terminal?

try:
which ruby
ruby -v

have you setup your shell path environment to include /usr/local/bin?

Dave.

>
>
>
> OK, so what did the Panther Install package screw up that the "ruby  
> install.rb" script wasn't smart enough to fix?
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[kimura wataru<ki...@us...>]

Thanks for your reporting. 

I wrote a patch to fix this problem.

----------
Index: install.rb
===================================================================
RCS file: /cvsroot/rubycocoa/src/install.rb,v
retrieving revision 1.17
diff -u -r1.17 install.rb
--- install.rb	2 Nov 2005 14:10:15 -0000	1.17
+++ install.rb	8 Dec 2005 13:58:57 -0000
@@ -563,7 +563,7 @@
 
   def extconf
     opt = @options['config-opt'].join(' ')
-    command "#{config('ruby-prog')} #{curr_srcdir}/extconf.rb #{opt}"
+    command "#{config('ruby-prog')} \"#{curr_srcdir}/extconf.rb\" #{opt}"
   end
 
   def config_dir_data( rel )
----------

Wed, Dec 7, 2005 5:58:37 PM, Dave Howell wrote:
>
>On Dec 7, 2005, at 17:50, Dave Howell wrote:
>
>> I guess I'll try compiling from source . . . .
>
>"ruby install.rb config" failed. It can't handles spaces in the path.
>
>I guess I'll have to relocate it to some directory that doesn't have 
>any spaces in its path . . .
>
>


-- 
kimura wataru

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave H. <gr...@gr...>]

On Dec 8, 2005, at 23:52, Dave Howell wrote:

>
> On Dec 8, 2005, at 4:00, Jonathan Paisley wrote:
>
>>
>> Try removing /Library/Frameworks/RubyCocoa.framework altogether and 
>> rerunning the source install.
>
> sudo rm  -R /Library/Frameworks/RubyCocoa.framework
> sudo ruby install.rb install
>
> Attempt to run "test"
> "can't open library: /usr/lib/libruby.1.dylib  (No such file or 
> directory, errno = 2)"

Eureka.


Ahem...


sudo rm  -R ~/Library/Frameworks/RubyCocoa.framework


Which just leaves the question of which program, when, installed the 
wrong version of the framework in my *user* /Library/Frameworks folder 
. . . . .

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Jonathan P. <jp...@dc...>]

On 9 Dec 2005, at 8:29, Dave Howell wrote:

> sudo rm  -R ~/Library/Frameworks/RubyCocoa.framework
>
> Which just leaves the question of which program, when, installed  
> the wrong version of the framework in my *user* /Library/Frameworks  
> folder . . . . .

Phew!

Good luck with 0.4.2 :)

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[kimura wataru<ki...@us...>]

Hi,

When environment DYLD_PRINT_LIBRARIES is set, the dynamic linker 
writes paths of loaded libraries to standard output.

ex)
zsh% DYLD_PRINT_LIBRARIES=1 ./MyApp.app/Contents/MacOS/MyApp 2>&1 | grep RubyCocoa 
dyld: loaded: /Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa


Fri, Dec 9, 2005 12:29:02 AM, Dave Howell wrote:
>
>On Dec 8, 2005, at 23:52, Dave Howell wrote:
>

>sudo rm  -R ~/Library/Frameworks/RubyCocoa.framework
>
>
>Which just leaves the question of which program, when, installed the 
>wrong version of the framework in my *user* /Library/Frameworks folder 
>. . . . .
>