On Sat, 2015-09-26 at 11:31 +0200, Marco Atzeri wrote:
> please note that
>
> lohit-gurmukhi-fonts
>
> is present on 64bit but missing from 32bit
Thanks, fixed:
https://github.com/cygwinports/lohit-gurmukhi-fonts/commit/c45f61f
--
Yaakov
--
Problem reports: http://cygwin.com/problems.
On 30/09/15 23:34, JonY wrote:
On 10/1/2015 00:05, David Stacey wrote:
On 30/09/15 12:15, JonY wrote:
gcc-5.2.0-1 has been uploaded for 32bit and 64bit Cygwin.
This is the first series of the 5.x releases, and should be considered
as experimental as such.
Have you managed to work around the
On 10/1/2015 00:05, David Stacey wrote:
> On 30/09/15 12:15, JonY wrote:
>> gcc-5.2.0-1 has been uploaded for 32bit and 64bit Cygwin.
>>
>> This is the first series of the 5.x releases, and should be considered
>> as experimental as such.
>
> Excellent - looking forward to trying this.
>
> Have y
Greetings, Eliot Moss!
> Dealing with "odd" characters like \ and such can be a pain, huh?
> Perhaps it will help you to know that bash will expand variables
> inside double-quoted arguments, i.e., "${src}". (You can write
> "$src" if you want, but over the years I am finding it clearer /
> bette
On 30/09/15 12:15, JonY wrote:
gcc-5.2.0-1 has been uploaded for 32bit and 64bit Cygwin.
This is the first series of the 5.x releases, and should be considered
as experimental as such.
Excellent - looking forward to trying this.
Have you managed to work around the ABI change in gcc-5 [1], or
gcc-5.2.0-1 has been uploaded for 32bit and 64bit Cygwin.
This is the first series of the 5.x releases, and should be considered
as experimental as such.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Un
Dealing with "odd" characters like \ and such can be a pain, huh?
Perhaps it will help you to know that bash will expand variables
inside double-quoted arguments, i.e., "${src}". (You can write
"$src" if you want, but over the years I am finding it clearer /
better to use the { } to make clear th
I sent this once and it did not appear in the list. Maybe I typed the
list name wrong?
I apologize if this appears twice.
I think the following code below should work (unfortunately, my email
program wants to wrap the code). The results of the echo
statement look fine! When I cut and paste the
> It seems a race problem, due to the repetitive fork of grep
> for every line of some-file
So why does it fail? Seems like a bug to me!
Regards,
Paul
>>>
>>> As does not fail on my computer, I suspect is a race between your AV and
>>> cygwin and sometimes cygwin wi
Am 30.09.2015 um 07:15 schrieb Bryan Tong:
Okay,
The plot thickens. After I renamed my home folder so Cygwin would make
a new one. The problem seems to be gone.
I will continue to test and see if it comes back. Maybe something in
my home folder is making it unhappy.
That sounds like it. Maybe s
Greetings, fluffy8x .!
>> I didn't see your reply beforehand as it didn't arrive in my inbox.
>> I'll retry and wait for autorebase to finish. Right now, though, it
>> seems that the process is hanging, as the progress bar does not
>> update.
> It turns out it just takes a long time; autorebase s
11 matches
Mail list logo