On 4/8/2013 12:13 AM, Federico Hernandez wrote:
Please upload.
---
wget -x -nH --cut-dirs=3 \
http://taskwarrior.org/download/cygwin17/task/setup.hint \
http://taskwarrior.org/download/cygwin17/task/task-2.2.0-1.tar.bz2 \
http://taskwarrior.org/download/cygwin17/task/task-2.2.0-1-src.
A new major version of task is available. Please refer to
http://taskwarrior.org/projects/taskwarrior/wiki/V220 for
detailed news and changelog information.
This is a recommended update.
Please upload.
---
wget -x -nH --cut-dirs=3 \
http://taskwarrior.org/download/cygwin17/task/setup.hint \
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.
my code is (with all added printf) :
static void
evsig_cb(
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 parent dir has 2775 permissions
and the subdirs
On 6 April 2013 22:37, Ken Brown wrote:
> D=http://sanibeltranquility.com/cygwin/64bit/release/alternatives
> wget -x -nH --cut-dirs=3 \
> ${D}/alternatives-1.3.30c-10-src.tar.bz2 \
> ${D}/alternatives-1.3.30c-10.tar.bz2 \
> ${D}/setup.hint
Done.
Thanks,
Andy
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 \
>> ${D}/emacs-X11/emacs-X11-24.3-3.tar.bz2 \
>> ${
Ken Brown writes:
> I recall something like this happening when I first switched to the
> new-style cygport files. The problem turned out to be that I wasn't
> giving the full name of the cygport file in the command line. If your
> file is `foo.cygport', you have to type
>
> cygport foo.cygport
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?
Yes.
Anyway, I've tried to compile a few packages, but cygport gives me
grief: it somehow doesn't pick up the version and rel
I've just set up a Cygwin64 system. It seems I can run a 32bit Cygwin
in parallel without disturbing anything, is that right?
Anyway, I've tried to compile a few packages, but cygport gives me
grief: it somehow doesn't pick up the version and release from new-style
cygport files and defines P ==
On 4/7/2013 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 ha
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 successfully built the 64bit cross compi
On 4/6/2013 11:10 PM, Corinna Vinschen wrote:
On Apr 6 21:44, marco atzeri wrote:
On 4/3/2013 4:22 PM, Corinna Vinschen wrote:
On Apr 3 15:30, marco atzeri wrote:
On 4/2/2013 10:59 AM, Corinna Vinschen wrote:
The crash occurs in a forked process, I guess. Since you're building
the stuff
12 matches
Mail list logo
