On Apr 7 16:57, marco atzeri wrote:
On 4/6/2013 11:27 PM, Corinna Vinschen wrote:
Unfortunately I can't upload. The 64bit/release/emacs dir has only
write permissions for Andy Koppe.
The same goes for yasm and libggi, which are 755 for Marco Atzeri
only. This is weird, the release
On Apr 7 14:37, Andy Koppe wrote:
On 6 April 2013 22:27, Corinna Vinschen wrote:
On Apr 6 16:50, Ken Brown wrote:
D=http://sanibeltranquility.com/cygwin/64bit/release/emacs
wget -x -nH --cut-dirs=3 \
${D}/emacs-24.3-3-src.tar.bz2 \
${D}/emacs-24.3-3.tar.bz2 \
On Apr 7 17:47, JonY wrote:
winpthreads is a pthreads implementation from mingw-w64. The ABI is
incompatible with pthreads-win32. One of the major differences is that
winpthreads uses scalar handles, so it is a bit more compatible to other
packages that assume int type handles.
I have
On Apr 7 19:12, marco atzeri wrote:
On 4/7/2013 9:06 AM, marco atzeri wrote:
On 4/6/2013 11:10 PM, Corinna Vinschen wrote:
What is the original code doing?
Corinna
I think the problem in on recv definition.
[...]
recv 4294967295
before for n 4294967295
[MARCOATZERI:03904]
On Apr 8 10:00, Corinna Vinschen wrote:
On Apr 7 19:12, marco atzeri wrote:
On 4/7/2013 9:06 AM, marco atzeri wrote:
On 4/6/2013 11:10 PM, Corinna Vinschen wrote:
What is the original code doing?
Corinna
I think the problem in on recv definition.
[...]
recv
On 4/8/2013 15:57, Corinna Vinschen wrote:
On Apr 7 17:47, JonY wrote:
winpthreads is a pthreads implementation from mingw-w64. The ABI is
incompatible with pthreads-win32. One of the major differences is that
winpthreads uses scalar handles, so it is a bit more compatible to other
packages
On Apr 8 18:14, JonY wrote:
On 4/8/2013 15:57, Corinna Vinschen wrote:
On Apr 7 17:47, JonY wrote:
winpthreads is a pthreads implementation from mingw-w64. The ABI is
incompatible with pthreads-win32. One of the major differences is that
winpthreads uses scalar handles, so it is a bit
Hi there!
Am 17.03.2013 17:45, schrieb Christopher Faylor:
I'd like to have a feel for how the 64-bit version of Cygwin will
impact package maintainers.
So, I'd appreciate some discussion about this.
1) Do you have a 64-bit version of Windows available?
Yes
3) Are you willing to download
On 4/7/2013 5:47 AM, JonY wrote:
For now, I intend to push it to 64bit Cygwin only, once gcc 4.7 for the
32bit cygwin hits release, I will push it there too.
There are some files in the package that replaces
e.g. conflict with
some of the
mingw-w64-headers CRT headers, this is done on
On 4/7/2013 7:11 AM, Achim Gratz wrote:
I've just set up a Cygwin64 system. It seems I can run a 32bit Cygwin
in parallel without disturbing anything, is that right?
FYI, unless I've misinterpreted, I think you need to use git master
cygport to build natively in cygwin64. If you're
Charles Wilson writes:
On 4/7/2013 7:11 AM, Achim Gratz wrote:
I've just set up a Cygwin64 system. It seems I can run a 32bit Cygwin
in parallel without disturbing anything, is that right?
FYI, unless I've misinterpreted, I think you need to use git master
cygport to build natively in
On 4/8/2013 12:04 PM, Corinna Vinschen wrote:
You're oh so right. Thanks for tracking this down. I'll fix that asap.
Should be fixed in CVS. I'll create a new 64 bit Cygwin DLL later today.
Corinna
it works fine,
thanks
Marco
@ coreutils
...
requires: bash libattr1 libgmp3 libiconv2 libintl8 tzcode
...
I think this should be libgmp10, not libgmp3. I noticed this because
expr reported an error during a fresh install, and expr worked only
after I installed libgmp10.
Ron
On 4/9/2013 03:58, Charles Wilson wrote:
Yes. I'm not sure how that should be handled. If you want to force the
switch, for that particular toolchain, then the cygwin package of the
mingw-w64-headers for that toolchain should probably stop shipping those
files, so that the (new) winpthreads
14 matches
Mail list logo
