Hi,
I have compiled and installed hydra in cygwin without any errors but iam
unable to run the hydra. It is giving me the following error message :
Rakesh@Rakesh-PC /usr/local/man/man1
$ run xhydra.1
run FATAL: Could not start C:\cygwin64\usr\local\man\man1\hydra.1
any help is very much apprici
On 21/03/2016 10:20, Rakesh Murarikar wrote:
Hi,
I have compiled and installed hydra in cygwin without any errors but iam
unable to run the hydra. It is giving me the following error message :
Rakesh@Rakesh-PC /usr/local/man/man1
$ run xhydra.1
run FATAL: Could not start C:\cygwin64\usr\local\m
Rakesh Murarikar snsin.com> writes:
> I have compiled and installed hydra in cygwin without any errors but iam
> unable to run the hydra. It is giving me the following error message :
>
> Rakesh Rakesh-PC /usr/local/man/man1
> $ run xhydra.1
> run FATAL: Could not start C:\cygwin64\usr\local\ma
On Mar 20 17:54, Houder wrote:
> Hi Corinna,
>
> A year ago you changed the "package choosing algorithm" ...
>
> https://sourceware.org/ml/cygwin/2015-02/msg00034.html
> - [ANNOUNCEMENT] Updated: setup.exe (Release 2.864) -- by Corinna Vinschen
> Here C. announces the modification of the "packag
Version 2.1.6-1 of
ncview
is available in the Cygwin distribution.
CHANGES
First release for Cygwin
DESCRIPTION
Ncview is a visual browser for netCDF format files.
Typically you would use ncview to get a quick and easy, push-button look
at your netCDF files. You can view simple movies of th
Thanks for the reply. Can you give me any solution for this?
--
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
On 2016-03-21 11:00, Corinna Vinschen wrote:
On Mar 20 17:54, Houder wrote:
Hi Corinna,
A year ago you changed the "package choosing algorithm" ...
[snip]
I'm using "Install from Local Directory: all the time (having a local
mirror dir) and it works fine for me. No idea what has gone diffe
On 21/03/2016 11:16, Rakesh Murarikar wrote:
Thanks for the reply. Can you give me any solution for this?
only suggestions as I am not planning to look on the sources:
- look on config and build logs
- check which variables are declared for the build
(eg __WIN32__, __CYGWIN__ ..and so on) t
I have just updated the mingw-w64 cross compilers Cygwin 32bit and
64bit to mingw64-*-gcc-5.3.0-1. This is a test version, all the caveats
for gcc-5.3.0 apply.
Note that C11 with gnu extensions is now default for C. See
https://gcc.gnu.org/gcc-5/porting_to.html for more help on porting code
to GC
JonY <10walls gmail.com> writes:
> I have just updated the mingw-w64 cross compilers Cygwin 32bit and
> 64bit to mingw64-*-gcc-5.3.0-1. This is a test version, all the caveats
> for gcc-5.3.0 apply.
Do you have your cygport packaging in public version control somewhere?
Otherwise I'll have to re
On 2016-03-21 11:00, Corinna Vinschen wrote:
On Mar 20 17:54, Houder wrote:
Hi Corinna,
A year ago you changed the "package choosing algorithm" ...
[snip]
I'm using "Install from Local Directory: all the time (having a local
mirror dir) and it works fine for me. No idea what has gone diffe
Achim Gratz nexgo.de> writes:
> You could have renamed the p7zip-15.09-2.cygwin.patch file or you could
> remove it and add these three lines to the cygport file:
Whoops, thanks, of course I forgot something dumb like that. Will give it
another go next time I'm using Windows.
Thanks,
Tony
--
On 3/21/2016 20:31, Tony Kelman wrote:
> JonY <10walls gmail.com> writes:
>
>> I have just updated the mingw-w64 cross compilers Cygwin 32bit and
>> 64bit to mingw64-*-gcc-5.3.0-1. This is a test version, all the caveats
>> for gcc-5.3.0 apply.
>
> Do you have your cygport packaging in public ve
Hi,
I had generated a FILE by simply doing a 'find' on a directory and used grep to
cull the results. I wasn't working so I repeated and tried the following
trivial 'grep':
% wc -l FILE
48786
% grep . FILE
2240
Very wrong.
I reverted to version 2.21 and everything now works as expected:
% g
On 2016-03-21 14:40, Gordon Grimes wrote:
Hi,
I had generated a FILE by simply doing a 'find' on a directory and
used grep to cull the results. I wasn't working so I repeated and
tried the following trivial 'grep':
% wc -l FILE
48786
% grep . FILE
2240
Very wrong.
I reverted to version 2.21
Gordon Grimes symantec.com> writes:
> % wc -l FILE
> 48786
> % grep . FILE
> 2240
>
> Very wrong.
You're aware that "." doesn't match empty lines?
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: h
On 2016-03-21 14:56, Achim Gratz wrote:
> Gordon Grimes writes:
>> % wc -l FILE
>> 48786
>> % grep . FILE
>> 2240
>>
>> Very wrong.
>
> You're aware that "." doesn't match empty lines?
Agreed, that is relevant, but there's the difference between v2.21 and v2.24...
On a whim and given that we do
On 21/03/2016 14:40, Gordon Grimes wrote:
Hi,
I had generated a FILE by simply doing a 'find' on a directory and used grep to
cull the results. I wasn't working so I repeated and tried the following
trivial 'grep':
% wc -l FILE
48786
% grep . FILE
2240
may be was a grep -c . FILE
Very w
Dear Mintty developers,
I'd like to volunteer to maintain a continuous integration build and
test environment for the Mintty project, here is a demo how it looks
like:
https://tea-ci.org/fracting/mintty/27
The CI script is pretty simple, only a few lines:
https://github.com/mintty/mintty/pull/52
On 03/21/2016 07:40 AM, Gordon Grimes wrote:
> Hi,
>
> I had generated a FILE by simply doing a 'find' on a directory and used grep
> to cull the results. I wasn't working so I repeated and tried the following
> trivial 'grep':
>
> % wc -l FILE
> 48786
> % grep . FILE
> 2240
>
> Very wrong.
On Mon, Mar 21, 2016 at 10:18 AM, Kenneth Wolcott
wrote:
> On Sat, Mar 19, 2016 at 8:56 AM, Corinna Vinschen
> wrote:
>> On Mar 18 14:50, Kenneth Wolcott wrote:
>>> Hi;
>>>
>>> I am using a daily refreshed Cygwin64 on WIndows 7 Enterprise.
>>>
>>> When I mount fairly large NetApp volumes and
On 3/17/16, Yaakov Selkowitz wrote:
> The old mingw.org (i686-pc-mingw32) toolchain has been removed from the
> Cygwin distribution. It was unmaintained (both upstream and downstream)
> and limited to 32-bit support.
>
> Users who wish to cross-compile for native Windows should use the
> mingw64-*
I'm seeing inconsistent results with cksum, with repeated
executions on the same file giving different results.
Now, I suspect I won't get much sympathy because I am
accessing the remote file through a "stone_age_old"*
(QNX4) Samba server through my Q: drive, but if there's
a solution to this, I'd
I have uploaded mintty 2.3.3 with the following changes:
Polished font configuration:
* Limit font warning to fonts with neither ANSI nor system locale
support (#527).
* Also include OEM/SYMBOL fonts with option -o ShowHiddenFonts=yes.
Highlights to previous major version (details see
htt
On Mon, Mar 21, 2016 at 4:21 PM, Nellis, Kenneth wrote:
> I'm seeing inconsistent results with cksum, with repeated
> executions on the same file giving different results.
> Now, I suspect I won't get much sympathy because I am
> accessing the remote file through a "stone_age_old"*
> (QNX4) Samba
On Mon, Mar 21, 2016 at 3:49 PM, Erik Soderquist
wrote:
> On Mon, Mar 21, 2016 at 4:21 PM, Nellis, Kenneth wrote:
>> I'm seeing inconsistent results with cksum, with repeated
>> executions on the same file giving different results.
>> Now, I suspect I won't get much sympathy because I am
>> acces
On Mon, Mar 21, 2016 at 5:09 PM, Nem W Schlecht wrote:
> On Mon, Mar 21, 2016 at 3:49 PM, Erik Soderquist
>> I expect if you did a capture of the traffic, you'd find the traffic
>> itself has inconsistent data...
>
> If the traffic was bad, I'd suspect the byte count to be off as well,
> but if th
On 3/22/2016 03:12, Lee wrote:
> On 3/17/16, Yaakov Selkowitz wrote:
>> The old mingw.org (i686-pc-mingw32) toolchain has been removed from the
>> Cygwin distribution. It was unmaintained (both upstream and downstream)
>> and limited to 32-bit support.
>>
>> Users who wish to cross-compile for nat
Greetings, Erik Soderquist!
> On Mon, Mar 21, 2016 at 4:21 PM, Nellis, Kenneth wrote:
>> I'm seeing inconsistent results with cksum, with repeated
>> executions on the same file giving different results.
>> Now, I suspect I won't get much sympathy because I am
>> accessing the remote file through
On Mon, Mar 21, 2016 at 8:28 PM, Andrey Repin wrote:
> Greetings, Erik Soderquist!
>> My first suspicion is that there is very little you can do from the
>> cygwin side outside of something like doing 5 consecutive tests and
>> take the most consistent result.
>
> Since SMB (especially in stone-ag
Thank you
Lee
On 3/21/16, JonY wrote:
> On 3/22/2016 03:12, Lee wrote:
>> On 3/17/16, Yaakov Selkowitz wrote:
>>> The old mingw.org (i686-pc-mingw32) toolchain has been removed from the
>>> Cygwin distribution. It was unmaintained (both upstream and downstream)
>>> and limited to 32-bit support.
31 matches
Mail list logo
