This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Rebase problems in Ruby
- From: Andrey Repin <anrdaemon at freemail dot ru>
- To: Chloe <starrychloe at oliveyou dot net>, cygwin at cygwin dot com
- Date: Sun, 3 Mar 2013 18:18:49 +0400
- Subject: Re: Rebase problems in Ruby
- References: <513330E4.4060100@oliveyou.net>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Chloe!
>> So where are these gems coming from and how many are there? Too
>> many/ones from unknown places are going to be either missed
>> by 'rubyrebase' or be impossible to fit in memory without
>> collision with other installed DLLs. See this thread for more
>> discussion of this:
> They come from 'bundle install' and 'gem install'. The standard Ruby
> places. There are about 100 in my Gemfile. The same project works on
> WinXP, but not Win8. I don't see how it can't fit in memory. My WinXP
> has 1GB and my Win8 has 8GB. I've run rebaseall and rubyrebase several
> times, and re-installed ImageMagick and libpixman_1.0 several times.
If they are "standard" fpr you, Cygwin may not know about them. You have to
manually supply a list of shared libs and applications your project depends
upon to rebase them on the same ground with the rest of Cygwin.
> I just can't get past this problem. Does this mean I have to give up on
> Cygwin?
> $ rails console
> 0 [main] ruby 6420 child_info_fork::abort:
> C:\cygwin\bin\cygpixman-1-0.dll: Loaded to different address:
> parent(0x68D70000) != child(0x35D0000)
> 0 [main] ruby 1500 child_info_fork::abort:
> C:\cygwin\bin\cygpixman-1-0.dll: Loaded to different address:
> parent(0x68D70000) != child(0x3720000)
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 03.03.2013, <18:17>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple