On 9/26/2013 01:20, Andrey Repin wrote:
> Greetings, JonY!
>
>> I sent an announcement about mingw64-*-headers and runtime update a few
>> days ago, but I don't see it. Did it go missing?
>
> Pathed on this side all fine.
>
Odd, I specifically disabled the gmail spam filter. If it is really out
Hi Andrey,
I am sorry I don't fully understand. I am a beginner try to get
something to work. What I am doing is that after pulling the .po I
need to create a .mo file.
https://github.com/AtelierConvivialite/webtranslateit/blob/master/examples/.wti#L11
On 25 September 2013 23:34, Andrey Repin wr
Thanks for your help
I got it to work with this line.
I: & cd I:\Work\GitHub\responsive\languages & c:\cygwin64\bin\bash -c
\cygdrive\i\Work\GitHub\responsive\languages\potomo.sh
and this file.
https://gist.github.com/grappler/6704735
On 25 September 2013 19:16, Andrey Repin wrote:
> Greetings,
Christopher Faylor sent the following at Wednesday, September 25, 2013 1:06 PM
>On Wed, Sep 25, 2013 at 04:59:57PM +, Buchbinder, Barry (NIH/NIAID)
>[E] wrote:
>>>Does setup for 64 bit cygwin need to be 64 bit? Might all this
>>be avoided if setup-x86_64.exe were itself 32 bit application?
>
>
Erwin Waterlander schreef, Op 25-9-2013 21:50:
Erwin Waterlander schreef, Op 24-9-2013 22:01:
Hi,
As far as I see it, on Cygwin it is assumed that man pages are
encoded in Latin-1 (ISO-8859-1).
For instance the man pages of vim.
/usr/share/man/fr/vim.1.gz is encoded in Latin-1.
$ export LA
On 9/25/2013 3:45 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
There's overhead to handle POSIX permissions, etc.
For one file, the effects of copying the meta-data should be negligible.
You're right. I didn't really look at the example (1 file) and the timing
difference (~10 sec). I was
On 09/25/2013 10:25 AM, Eric Blake wrote:
> On 09/25/2013 09:04 AM, Christopher Faylor wrote:
>>
>> Since you've previously made modifications in this area, why not supply
>> a simple patch?
>
> Ah - the joys of having write access. Yes, I'll post a patch for
> discussion.
What am I getting myse
Erwin Waterlander schreef, Op 24-9-2013 22:01:
Hi,
As far as I see it, on Cygwin it is assumed that man pages are encoded
in Latin-1 (ISO-8859-1).
For instance the man pages of vim.
/usr/share/man/fr/vim.1.gz is encoded in Latin-1.
$ export LANG=fr_FR.UTF-8
$ man vim
This will show the Fre
> There's overhead to handle POSIX permissions, etc.
For one file, the effects of copying the meta-data should be negligible.
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: h
On 9/25/2013 2:36 PM, KARR, DAVID wrote:
Looks fine. I'm out of ideas. Maybe Chuck (the run and run2
maintainer) can help you if you want to pursue this.
Anyone else (Chuck?) have any ideas on this? As I can't open Emacs
from the shortcut anymore, my current workaround is opening an rxvt
win
Greetings, Wm. David Bentlage!
> I've often noticed that there's a big difference in the performance
> between Cygwin cp and Windows copy over the local network -- cp
> usually takes twice as long for the same operation. Here's an
> example:
> muser@A4826995 /c/Users/Muser
> $ time cmd /c copy \
On 9/25/2013 1:17 PM, Wm. David Bentlage wrote:
Greetings,
I've often noticed that there's a big difference in the performance
between Cygwin cp and Windows copy over the local network -- cp
usually takes twice as long for the same operation. Here's an
example:
muser@A4826995 /c/Users/Muser
$
Greetings, Ulrich Pogson!
> I would like to run this script `for file in `find . -name "*.po"` ;
> do msgfmt -o ${file/.po/.mo} $file ; done` in windows cmd.
I think you mean "command line" and not a "script".
This is not realistically possible. Windows CMD do not have as straightforward
quoting
Greetings,
I've often noticed that there's a big difference in the performance
between Cygwin cp and Windows copy over the local network -- cp
usually takes twice as long for the same operation. Here's an
example:
muser@A4826995 /c/Users/Muser
$ time cmd /c copy server\\w\\cygwin.zip .
On Wed, Sep 25, 2013 at 04:59:57PM +, Buchbinder, Barry (NIH/NIAID) [E]
wrote:
>Does setup for 64 bit cygwin need to be 64 bit? Might all this
>be avoided if setup-x86_64.exe were itself 32 bit application?
I lost that argument. Apparently some 64-bit systems can't run 32-bit
applications.
Greetings, Larry Hall (Cygwin)!
>> In fact, what would be the issue to set the requested execution level
>> to "asInvoker" for the official setup-x86_64.exe?
>> People with admin rights will still be able to install for all users
>> and people without admin rights will be able to install for
>> th
Does setup for 64 bit cygwin need to be 64 bit? Might all this
be avoided if setup-x86_64.exe were itself 32 bit application?
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cyg
On 09/25/2013 09:04 AM, Christopher Faylor wrote:
>
> Since you've previously made modifications in this area, why not supply
> a simple patch?
Ah - the joys of having write access. Yes, I'll post a patch for
discussion.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualizati
On Wed, Sep 25, 2013 at 10:43:58AM +0200, Andreas Steenpass wrote:
>Please consider the following testcase:
Should be fixed in the upcoming snapshot (and eventually in 1.7.26).
Thanks for the test case.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://c
On 9/25/2013 11:21 AM, Frédéric Bron wrote:
In fact, what would be the issue to set the requested execution level
to "asInvoker" for the official setup-x86_64.exe?
People with admin rights will still be able to install for all users
and people without admin rights will be able to install for
them
> There is no reason why it has to be. mpress *is* used to compress the
> official setup x86_64 binary. Earnie posted a link.
I get the following error:
PE32+/x64 2544.0kB -- MPRESS: TLS callbacks are not supported in this version.
Any idea?
Frédéric
--
Problem reports: http://cygwin.com
Currently, git-svn of Cygwin is unusable because of this:
http://git.661346.n2.nabble.com/Git-pm-with-recent-File-Temp-fail-td7580381.html
FYI, it was fixed on git 1.8.3:
https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.3.txt
--
Problem reports: http://cygwin.com/problems.h
>> In fact, what would be the issue to set the requested execution level
>> to "asInvoker" for the official setup-x86_64.exe?
>> People with admin rights will still be able to install for all users
>> and people without admin rights will be able to install for
>> them-selves.
>
>
> Doesn't that mea
I have just updated the CRT and runtime libraries for the mingw-w64
cross compilers, along with the w32api for Cygwin 32bit and 64bit.
mingw64-*-headers-3.0.0-1
mingw64-*-runtime-3.0.0-1
w32api-{headers,runtime}-3.0.0-1
The cross compiler can produce Win32 and Win64 native binaries. As a
cross c
On Wed, Sep 25, 2013 at 04:09:22PM +0200, Fr?d?ric Bron wrote:
>What is the usual compressing tool used for setup-x86_64.exe? I cannot
>use upx as it does not support x86_64 binaries. Some suggest mpress
>but it is not part of cygwin packages.
There is no reason why it has to be. mpress *is* us
On Wed, Sep 25, 2013 at 06:05:07AM -0600, Eric Blake wrote:
>On 09/24/2013 10:32 PM, Christopher Faylor wrote:
>
>>> This patch causes failures on at least test-fcntl and test-dup2 on
>>> cygwin (both 32-bit and 64-bit); there, getdtablesize() currently
>>> returns the current runtime value, but th
On 9/25/2013 10:11 AM, Frédéric Bron wrote:
In fact, what would be the issue to set the requested execution level
to "asInvoker" for the official setup-x86_64.exe?
People with admin rights will still be able to install for all users
and people without admin rights will be able to install for
t
When I open a cygwin terminal, a tilde (~) is written to the command
line. Then, every 20 seconds (aprox) I get another tilde and so on, as
the window keeps focused. So that I get wrong commands written.
Anyone with this issue?
[Setup.exe version 2.819 (32 bit)]
Thanks
--
Problem reports:
On 9/25/2013 02:24, wynfi...@gmail.com wrote:
"Your vendor has not defined Fcntl macro O_EXLOCK,"
O_EXLOCK is a BSD feature, and Cygwin tries to emulate Linux, not BSD.
Minimal testing tells me you can use Cygwin's nonstandard
F_LCK_MANDATORY feature from Perl. This script, foo.pl, doesn't
On 9/25/2013 00:33, Ulrich Pogson wrote:
after try everything I could not get it to work.
If my other post to this thread doesn't help, post the errors you get.
You're making us guess what is wrong with "everything", and we don't
know what's wrong with "everything". :)
--
Problem reports:
> I just modified this:
> Index: setup64.exe.manifest
> ===
> RCS file: /cvs/cygwin-apps/setup/setup64.exe.manifest,v
> retrieving revision 2.1
> diff -r2.1 setup64.exe.manifest
> 25c25
> < uiAccess="false"/>
> ---
>>
On 9/24/2013 15:43, Ulrich Pogson wrote:
I would like to run this script `for file in `find . -name "*.po"` ;
do msgfmt -o ${file/.po/.mo} $file ; done` in windows cmd.
What exactly do you mean by "in windows cmd"?
If you're trying to translate this script into cmd.exe's "batch"
language, it
Hi,
What is the usual compressing tool used for setup-x86_64.exe?
I cannot use upx as it does not support x86_64 binaries.
Some suggest mpress but it is not part of cygwin packages.
Frédéric
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
D
>> Trying to compress it with upx failed with an error message:
>> upx: setup-x86-64.exe: CantPackException: can't pack new-exe
>
> UPX can't compress PE+ (64bit) executables.
That's right, I have the same issue.
Frédéric
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On 09/24/2013 10:32 PM, Christopher Faylor wrote:
>> This patch causes failures on at least test-fcntl and test-dup2 on
>> cygwin (both 32-bit and 64-bit); there, getdtablesize() currently
>> returns the current runtime value, but this value starts at 256, and
>> automatically expands as needed at
On Wed, Sep 25, 2013 at 3:41 AM, Achim Gratz wrote:
> Am 24.09.2013 23:49, schrieb Buchbinder, Barry (NIH/NIAID) [E]:
>>
>> Trying to compress it with upx failed with an error message:
>> upx: setup-x86-64.exe: CantPackException: can't pack new-exe
So others are using mpress instead. http://www.ma
Hi,
I sent an announcement about mingw64-*-headers and runtime update a few
days ago, but I don't see it. Did it go missing?
signature.asc
Description: OpenPGP digital signature
Please consider the following testcase:
#include
#include
#include// compile with -lpthread or -pthread
void atfork_prepare()
{
printf("atfork_prepare, pid: %d\n", getpid());
}
void atfork_parent()
{
printf("atfork_parent, pid: %d\n", getpid());
}
void atfork_
Re: Perl 5, version 14, subversion 2 (v5.14.2)
Cygwin: CYGWIN_NT-5.1 1.7.25(0.270/5/3
In Perl (I am attempting to open a file and put an exclusive lock on it to
update
it like this:
###
use Fcntl qw( O_RDWR O_CREAT O_NONBLOCK O_EXLOCK );
Am 24.09.2013 23:49, schrieb Buchbinder, Barry (NIH/NIAID) [E]:
Trying to compress it with upx failed with an error message:
upx: setup-x86-64.exe: CantPackException: can't pack new-exe
UPX can't compress PE+ (64bit) executables.
Regards,
Achim.
--
Problem reports: http://cygwin.com/
40 matches
Mail list logo
