On 7/16/2015 10:06 AM, jari wrote:
On 2015-07-15 16:12, Ken Brown wrote:
| On 7/15/2015 2:28 PM, Corinna Vinschen wrote:
| On Jul 15 16:24, Marco Atzeri wrote:
| Dear All,
| I spent a bit of time checking the real situation of the packages
| still missing as 64 bit port.
| After xdelta, bsdiff
Written by a practitioner, you will get your investment back many times
over.
Go to www.procurementbusinessskills.com and www.practicalbusinessskills.com
50% discount.
If not entirely satisfied guaranteed money back.
B. Hughes MSc MCIPS
[M] 0746-222-7806
[W]
Written by a practitioner, you will get your investment back many times
over.
Go to www.procurementbusinessskills.com and www.practicalbusinessskills.com
50% discount.
If not entirely satisfied guaranteed money back.
B. Hughes MSc MCIPS
[M] 0746-222-7806
[W]
On 2015-07-16 10:10, Marco Atzeri wrote:
| On 7/16/2015 10:06 AM, jari wrote:
| On 2015-07-15 16:12, Ken Brown wrote:
| | On 7/15/2015 2:28 PM, Corinna Vinschen wrote:
| | On Jul 15 16:24, Marco Atzeri wrote:
| | Dear All,
| | I spent a bit of time checking the real situation of the packages
| |
On 2015-07-15 16:24, Marco Atzeri wrote:
| Dear All,
| I spent a bit of time checking the real situation of the packages
| still missing as 64 bit port.
| After xdelta, bsdiff and iperf porting, without counting the few mingw ones,
| the duplicates we are down to ~44.
|
| Please see here the
On 2015-07-15 16:12, Ken Brown wrote:
| On 7/15/2015 2:28 PM, Corinna Vinschen wrote:
| On Jul 15 16:24, Marco Atzeri wrote:
| Dear All,
| I spent a bit of time checking the real situation of the packages
| still missing as 64 bit port.
| After xdelta, bsdiff and iperf porting, without counting
Hi,
I am seeing an issue when I run msbuild where I will get msbuild:
command not found.
Invoke msbuild.exe in stead ... invocation of msbuild will not work,
because there is a
directory msbuild.
Or: include the following in your .bashrc:
alias msbuild='MSBuild.exe -nologo'
Henri
--
On 15/07/2015 20:56, Bob Goldberg wrote:
I've been running cygwin/x (x86) under xp pro for YEARS,
with it working perfectly.
The last update to 1.17 has been a disaster.
I've read about using -listen tcp, and DISPLAY=:0.0 ;
however, nothing I've tried resolves the seg fault error i'm getting.
Hi,
I am seeing an issue when I run msbuild where I will get msbuild: command not
found. I will then run which msbuild, where it will then tell me no msbuild
in The path to msbuild is within PATH, so it should be able to find it.
I did a check to make sure that msbuild does exist in the
On 7/16/2015 8:35 PM, Achim Gratz wrote:
jari writes:
This is the command that fails (from debugging pristine-tar):
xdelta delta -0 --pristine /tmp/pristine-tar.joIgDIVU9F/recreatetarball
/tmp/pristine-tar.9DVOtZUF7E/origtarball /tmp/pristine-tar.9DVOtZUF7E/deltaxdel
So, the option missing
On Thu, Jul 16, 2015 at 9:30 PM, Andrey Repin wrote:
Linux grep will do the same.
null byte = not a text.
Wrong encoding, not matching locale = not a text.
I have repeatedly asked you to stay out of my threads. My experience is you
typically misread, misunderstand or misrepresent most or all
Steven Penny svnpenn-at-gmail.com |cygwin_ml_nodigest| wrote at 20:29 -0500 on
Jul 16, 2015:
Consider this command:
printf 'alpha\nbravo\ncharlie\n' | grep --line-regexp --quiet bravo
grep sees 3 lines separated by newline, and matches the bravo line. Now
consider
this command:
The following packages have been updated in the Cygwin distribution:
* dri-drivers-10.6.2-1
* libEGL1-10.6.2-1
* libEGL-devel-10.6.2-1
* libGL1-10.6.2-1
* libGL-devel-10.6.2-1
* libGLESv2_2-10.6.2-1
* libGLESv2-devel-10.6.2-1
* libglapi0-10.6.2-1
* libOSMesa8-10.6.2-1
* libOSMesa-devel-10.6.2-1
*
On Jul 16, 2015, at 10:04 PM, Steven Penny svnp...@gmail.com wrote:
On Thu, Jul 16, 2015 at 9:30 PM, Andrey Repin wrote:
Linux grep will do the same.
null byte = not a text.
Wrong encoding, not matching locale = not a text.
I have repeatedly asked you to stay out of my threads. My
Greetings, John Hein!
cygwin grep is detecting the input as binary which seems to be
overriding the 'match the whole line' behavior of --line-regexp. Get
rid of --quiet to see that.
That does seem like a bug in the cygwin implementation of grep to me.
Linux grep will do the same.
null byte
On Thu, Jul 16, 2015 at 9:04 PM, John Hein wrote:
cygwin grep is detecting the input as binary which seems to be
overriding the 'match the whole line' behavior of --line-regexp. Get
rid of --quiet to see that.
It appears to be intended behavior starting with version 2.21:
If a file contains
The following packages have been updated in the Cygwin distribution:
* dri-drivers-10.6.2-1
* libEGL1-10.6.2-1
* libEGL-devel-10.6.2-1
* libGL1-10.6.2-1
* libGL-devel-10.6.2-1
* libGLESv2_2-10.6.2-1
* libGLESv2-devel-10.6.2-1
* libglapi0-10.6.2-1
* libOSMesa8-10.6.2-1
* libOSMesa-devel-10.6.2-1
*
Consider this command:
printf 'alpha\nbravo\ncharlie\n' | grep --line-regexp --quiet bravo
grep sees 3 lines separated by newline, and matches the bravo line. Now consider
this command:
printf 'alpha\0bravo\0charlie\0' | grep --line-regexp --quiet bravo
My thinking tells me that
18 matches
Mail list logo
