Re: Shouldn't gcc-4 depend on libmpfr4 ?

2013-03-03 Thread Achim Gratz
marco atzeri gmail.com> writes: > should be libmpfr4 instead of libmpfr1. It looks like cc1 is linked against libmpfr1 _and_ libmpfr4, so they should both be listed as dependencies. Regards, Achim. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.

Re: Rebase problems in Ruby

2013-03-03 Thread Cygwin/X
On Sun, 03 Mar 2013 06:15:48 -0500, Chloe wrote: > > 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 thre

Unix domain accept() and getperrname() doesn't return the client address.

2013-03-03 Thread Tanaka Akira
Hi. I found that accept() and getperrname() on a Unix domain socket doesn't return the client socket address. The sun_path field of the returned address is empty. Is it an intentional behavior? % uname -srvm CYGWIN_NT-5.1 1.7.18s(0.263/5/3) 20130301 15:56:19 i686 % ls tst-client.c tst-server.c

Re: Rebase problems in Ruby

2013-03-03 Thread Eliot Moss
On 3/3/2013 3:05 PM, Chloe wrote: /usr/bin/ruby.exe: skipped because not rebaseable If any existing process has the file open, you would see this. There might be other causes as well. Unfortunately I must forgo Cygwin for native Windows executables. While rebase problems can indeed be a bi

Re: Rebase problems in Ruby

2013-03-03 Thread Chloe
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. FYI, I saw these lines in the output. I don't know if they are relevant. Notice

Re: segfault in recent snapshots

2013-03-03 Thread Christopher Faylor
On Sun, Mar 03, 2013 at 12:02:43PM +, Henry S. Thompson wrote: >Christopher Faylor writes: > >> On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: >>>Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous >>>thread?) >> >> "previous thread"? > >http://cygwin.10696

Re: segfault in recent snapshots

2013-03-03 Thread marco atzeri
On 3/3/2013 1:02 PM, Henry S. Thompson wrote: Christopher Faylor writes: On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous thread?) "previous thread"? http://cygwin.1069669.n5.nabble.com/psql-crashes-wit

Re: Rebase problems in Ruby

2013-03-03 Thread Andrey Repin
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:

Re: ViM block cursor under screen

2013-03-03 Thread David T-G
Brian -- ...and then Brian W. Neu said... % % So I was lucky enough to find that the following in my .vimrc enabled a % block cursor when launching vim under a cygwin terminal: Hey, cool! That's great to know. ... % % But when I launch vim under screen under a terminal, the block cursor % di

Re: segfault in recent snapshots

2013-03-03 Thread Henry S. Thompson
Christopher Faylor writes: > On Sat, Mar 02, 2013 at 08:00:38PM +, Henry S. Thompson wrote: >>Snapshots of 31/1 and 1/3 are giving segfaults for psql (see previous >>thread?) > > "previous thread"? http://cygwin.1069669.n5.nabble.com/psql-crashes-with-snapshot-td96270.html >>and locally comp

Re: Rebase problems in Ruby

2013-03-03 Thread 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