Ruby 1.8.7 for Wary 5.5 i686 Architecture (Untested)

discuss compiling applications for Puppy
Post Reply
Message
Author
s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

Ruby 1.8.7 for Wary 5.5 i686 Architecture (Untested)

#1 Post by s243a »

Again on my quest to bring the Mindori browser to Wary 5.5 I compiled Ruby (as a pet file):
http://www.pearltrees.com/s243a/ruby-1- ... m163639672

It chose the Ruby version that was released around the time of Wary 5.5. I need Ruby to compile libnotify,
http://www.pearltrees.com/s243a/libnoti ... id15167199

which is needed for Madori. This pet has not been tested. The test will be me succeeding to get the Mindori browser to work. Also note that my system seems to be targeting i686 by default. Should I try to target and older architecture since Wary is for older computers?, and if so how?
Last edited by s243a on Mon 14 Dec 2015, 06:08, edited 2 times in total.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#2 Post by s243a »

I'm having an issue but I don't think it is related to the pet. I'm trying to install rubygems and I'm getting the error

Code: Select all

./lib/rubygems.rb:8:in `require`:no such file to load -- rbconfig (LoadError)
but rbconfig exits on my system and the path is:

Code: Select all

/lib/ruby/1.8/i686-linux/rbconfig.rb
I'm executing the installation as follows:

Code: Select all

ruby -T0 -IDirectory=/lib/ruby/1.8/ -IDirectory=/lib/ruby/1.8/i686-linux/ setup.rb
I saved some links related to this issue here:
http://www.pearltrees.com/s243a/rubylib ... id15172131

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#3 Post by s243a »

So I see a problem here:

Code: Select all

ruby -I '/lib/ruby/1/8' -e 'puts  $LOAD_PATH' $>bla.txt
produces:

Code: Select all

/lib/ruby/1.8
/lib/ruby/1.8
/lib/ruby/i686-linux/
/tmp/ruby-1.8.7-p357/lib/ruby/site_ruby/1.8
/tmp/ruby-1.8.7-p357/lib/ruby/site_ruby/1.8/i686-linux
/tmp/ruby-1.8.7-p357/lib/ruby/site_ruby
/tmp/ruby-1.8.7-p357/lib/ruby/vendor_ruby/1.8
/tmp/ruby-1.8.7-p357/lib/ruby/vendor_ruby/1.8/i686-linux
/tmp/ruby-1.8.7-p357/lib/ruby/vendor_ruby
/tmp/ruby-1.8.7-p357/lib/ruby/1.8
/tmp/ruby-1.8.7-p357/lib/ruby/1.8/i686-linux
and this is because when I compiled I set

Code: Select all

--prefix=/tmp/ruby-1.8.7-p357/
so that I could compile everything to one directory and then run dir2pet. Perhaps I should add a post installs script to the pet file to strip off the /tmp/ruby-1.8.7-p357/ in the LOAD_PATH. Not sure how to add a post install script to a pet package but I'm sure google can tell me.

However, while this variable is set wrong, I thought the command line options I supplied above should have circumvented this incorrect installation.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#4 Post by s243a »

I fixed the above pet so the load path is correct.
(See this thread)



I tested it by compiling ruby gems. Ruby should work now. However, I now have an untested version of ruby gems:
ruby-gems2.2.0.pet (for wary 5.5)

which I'll test tomorrow.

Post Reply