From: "Bill C." Date: 2013-05-18T08:27:35+09:00 Subject: Re: Mac OS 10.8.2 and openssl Hey, I have a radical and crazy idea. How about, instead of having every single person who wants to install ruby and gems on OSX have to jump through this stupid series of ridiculous hoops, the relatively few ruby DEVELOPERS actually fix the build configuration (for OS X and others as well)? The man-hours spent this way are all upside down. Fix it at the head, not at the tail. This kind of hopeless head-banging by all of us is an idiotic expectation. The fact that "--with-openssl-dir" apparently throws meaningless errors (or are they meaningful, and how the hell are we supposed to know?) proves that ruby devs aren't minding the store. Someone(s) who _understand(s)_ the "configure" and "automake" setup should actually provide documentation for --with-openssl-dir and --with-out-tcl and --with-out-tk and the dozens of other parameters that cause lots of errors that the build plows right through. Use these parameters at all and have the system bark at you. And expect them to have no effect as well, in my experience. A ruby USER shouldn't have to know everything that the ruby DEVS do, but we are getting closer to it with every release. This is only one more thing to really make it a pain in the neck for every OSX ruby user out here. It almost feels like ruby devs want to make ruby such a pain to build or install that the rest of us will give up on it. Better yet, Apple, how about releasing ruby 2.0 with your next iteration of OS X? OK, now I'm obviously hallucinating. -- Posted via http://www.ruby-forum.com/.