On Fri, 2011-01-28 at 13:08 -0500, Charles Wilson wrote:
> Well, the library components appear to operate correctly. However, the
> executable, iconv.exe, does not do so. It picked up an dependency on a
> new symbol, _feinitialize, by being compiled against the 1.7.8.
>
> So, consider this versi
On Tue, 2011-03-01 at 01:08 +0100, Paul Maier wrote:
> Hi,
>
> my gvim dies when I select file->open from gvim's menu (see screenshot in
> file gvim.jpg.uuencode.txt).
> 100 % reproducable.
> Same, if I start gvim with a file to edit or without.
WFM. How are you starting gvim?
Yaakov
--
Pr
Hello list,
I generally set most of my environment variables in the System control
panel for my user, instead of in my .bashrc/.zshrc
I noticed that when I log in to Cygwin via ssh, these environment
variables are not available.
Would this be considered a misfeature?
I'll probably hack together
On 3/1/2011 2:38 PM, Christopher Faylor wrote:
> On Tue, Mar 01, 2011 at 01:11:38PM -0800, David Rothenberger wrote:
>> On 3/1/2011 12:59 PM, David Rothenberger wrote:
>>> I just ran into the dreaded winmm.dll error 487 again from git using
>>> 1.7.8. This time, the error doesn't occur with "git lo
> On 03/01/2011 04:57 PM, Tim Coalson wrote: > > The problem: > > > > $
> /bin/ls
>-l /proc/sys/Device > > > > hit enter, and my system instantly reboots,
>without
>shutdown. Without the -l > > option, works fine. Unfortunately, ls with
>colors enabled also causes this > > behavior, even
On 03/01/2011 04:57 PM, Tim Coalson wrote:
> The problem:
>
> $ /bin/ls -l /proc/sys/Device
>
> hit enter, and my system instantly reboots, without shutdown. Without the -l
> option, works fine. Unfortunately, ls with colors enabled also causes this
> behavior, even without -l, as in:
>
> $
On Tue, Mar 01, 2011 at 02:53:40PM -0800, David Rothenberger wrote:
>I'll keep an eye out for a snapshot to test.
It's there now.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubsc
On 3/1/2011 2:38 PM, Christopher Faylor wrote:
> On Tue, Mar 01, 2011 at 01:11:38PM -0800, David Rothenberger wrote:
>> On 3/1/2011 12:59 PM, David Rothenberger wrote:
>>> I just ran into the dreaded winmm.dll error 487 again from git using
>>> 1.7.8. This time, the error doesn't occur with "git lo
On 3/1/2011 2:37 PM, Christopher Faylor wrote:
On Tue, Mar 01, 2011 at 02:03:24PM -0800, Hans Horn wrote:
Great job, Corinna,
H.
Sigh.
cgf
Congrats to Corinna, cgf, and all the other partners in crime.
Hope I didn't miss anybody.
--
Problem reports: http://cygwin.com/problems.html
On Tue, Mar 01, 2011 at 01:11:38PM -0800, David Rothenberger wrote:
>On 3/1/2011 12:59 PM, David Rothenberger wrote:
>> I just ran into the dreaded winmm.dll error 487 again from git using
>> 1.7.8. This time, the error doesn't occur with "git log" but happens
>> when running "git svn rebase --all"
On Tue, Mar 01, 2011 at 02:03:24PM -0800, Hans Horn wrote:
>Great job, Corinna,
>H.
Sigh.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#un
Thanx a gazillion!
All the intermittent forking problems and most of the "bad address"
problems I've been seeing have gone.
The only "bad address" problem (that I never noticed before) was:
/usr/bin/tput: bad address
-rwxrwx---+ 1 hans xxx 12302 2010-01-02 07:23:15 /usr/bin/tput
As usual, no
On Tue, Mar 1, 2011 at 9:51 AM, Corinna Vinschen wrote:
> I just released 1.7.8-1. This release fixes a bunch of bugs and a
> moderate amount of new features.
Thanks. Fork speed is up 23% on my 2K8R2 system!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http:/
On Tue, Mar 1, 2011 at 3:26 AM, Frederik wrote:
> Great! Thanks!
>
>> shopt -s completion_strip_exe
Can that be made the default, along with EXECIGNORE=*.dll ?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cy
On 3/1/2011 12:59 PM, David Rothenberger wrote:
> I just ran into the dreaded winmm.dll error 487 again from git using
> 1.7.8. This time, the error doesn't occur with "git log" but happens
> when running "git svn rebase --all". I guess that will make it pretty
> hard to reproduce.
>
> I'll try th
A new release of m4, 1.4.16-1, will soon be available for download on a
mirror near you, leaving 1.4.15-1 as previous.
NEWS
This is a new upstream release, with upstream NEWS attached. See also
/usr/share/doc/m4/.
You must rebuild from source if you want the experimental changeword
feature
I just ran into the dreaded winmm.dll error 487 again from git using
1.7.8. This time, the error doesn't occur with "git log" but happens
when running "git svn rebase --all". I guess that will make it pretty
hard to reproduce.
I'll try this with the 20110227 snapshot as soon as I can.
--
David R
On Mar 1 18:57, Rainer Emrich wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Corinna,
>
> I'm not so sure if that's a ld problem, see the following thread:
>
> http://sourceware.org/ml/cygwin/2010-12/msg00448.html
>
> I haven't tried 1.7.6, but as Yaakov mentions there is a chang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corinna,
I'm not so sure if that's a ld problem, see the following thread:
http://sourceware.org/ml/cygwin/2010-12/msg00448.html
I haven't tried 1.7.6, but as Yaakov mentions there is a change in behaviour in
August last year.
Rainer
P.S.: please
Hi Cygwin friends and users,
I just released 1.7.8-1. This release fixes a bunch of bugs and a
moderate amount of new features.
Most notably is perhaps the return of the ability to delete empty
directories which are current working directory of other (or the own)
Cygwin processes. Using an unf
On Mar 1 18:26, Rainer Emrich wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Any news on this issue?
>
> At the moment it's impossible to build libgcj during bootstrap of gcc!
>
> I tried 1.7.7-1 and the snapshot 20110227.
>
> Here some diagnostic:
>
> 288 117500220 [main] ld
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any news on this issue?
At the moment it's impossible to build libgcj during bootstrap of gcc!
I tried 1.7.7-1 and the snapshot 20110227.
Here some diagnostic:
$ /SCRATCH/tmp.ALIlKIg0qU/gcc-4.5.0-1/gcc-4.5.0-1/./gcc/xgcc -shared-libgcc
- -B/SCRATCH
On 2/28/2011 11:06 PM, Christopher Faylor wrote:
> On Fri, Feb 25, 2011 at 04:09:44PM -0800, David Rothenberger wrote:
>> On 2/25/2011 3:24 PM, David Rothenberger wrote:
>>> I realize this report won't be terribly useful, but I did encounter
>>> a problem with the latest snapshot. I have a local gi
> Anyway I upgraded everything and now I am fine.
That's good.
As I commented in the other thread, I don't really know which versions of
Cygwin or other libraries will work with Unison, or any of my other
packages. I just compile and release them. For the most part that seems
to work - yours is
On 3/1/2011 1:46 PM, Andy Koppe wrote:
Good idea, although that would entail unnecessary (and unwanted)
updates, for example, the Cygwin DLL would get updated whatever
package you installed, even if the package was built years ago.
Indeed and upgrading Cygwin itself is the very thing I was tryi
On 3/1/2011 8:20 AM, Andy Koppe wrote:
To be fair, setup.exe ought to be able to resolve or warn about such
version dependencies.
That's what I was tempted to say. For the record this is what I did:
1) select Keep
2) manually pick unison
3) accept the dialog about dependencies
Yet AFAICT only U
> >> Which is the problem: the unison command was compiled against a newer
> >> cygwin1.dll than yours.
> >
> > To be fair, setup.exe ought to be able to resolve or warn about such
> > version dependencies. Unfortunately the infrastructure for that isn't
> > in place, as it would require version r
On 1 March 2011 10:57, Matthias Andree wrote:
> Am 01.03.2011 08:20, schrieb Andy Koppe:
>> On 28 February 2011 19:52, Matthias Andree wrote:
>
>>> Which is the problem: the unison command was compiled against a newer
>>> cygwin1.dll than yours.
>>
>> To be fair, setup.exe ought to be able to resol
Great! Thanks!
shopt -s completion_strip_exe
Andy
--
Frederik
freak.f...@gmail.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsub
Am 01.03.2011 08:20, schrieb Andy Koppe:
> On 28 February 2011 19:52, Matthias Andree wrote:
>> Which is the problem: the unison command was compiled against a newer
>> cygwin1.dll than yours.
>
> To be fair, setup.exe ought to be able to resolve or warn about such
> version dependencies. Unfortu
On 1 March 2011 09:40, Frederik wrote:
> I wonder if it's possible to omit `.exe' when completing a command in cygwin
> shell.
Yep, bash-4.1 has an option for that:
shopt -s completion_strip_exe
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.
Hey there!
I wonder if it's possible to omit `.exe' when completing a command in
cygwin shell. Now `mkd' completes to `mkdir.exe', but completion to
`mkdir' would be nicer imho...
Thanks & Regards,
Fred
--
Frederik
freak.f...@gmail.com
--
Problem reports: http://cygwin.com/problems.
The httping 1.4.4-1 package contains a file name with asterisk:
$ cygcheck -l httping
/usr/bin/httping.exe
/usr/share/doc/Cygwin/httping-1.4.4.README
/usr/share/doc/httping/license.txt
/usr/share/doc/httping/readme.txt
/usr/share/man/man1/httping.1.gz
/usr/share/man/man1/*.1.gz
http://cygwin.com/
On Feb 28 16:49, Fergus wrote:
> Thanks to a previous responder I now know that in response to uname:
NT-4.0 = NT4
> NT-5.0 = W2000
> NT-5.1 = XP
NT-5.2 = Windows 2003 as well as 64 bit XP
> NT-6.0 = Vista
> NT-6.1 = W7
>
> Q1 Can anybody please tell me the corresponding information for W9
34 matches
Mail list logo
