ANNOUNCING Tahoe, the Lofty-Atmospheric Filesystem, v1.5

Dear people of cygwin@cygwin.com: We've used cygwin to develop Tahoe-LAFS from the beginning, and we maintain a buildbot which builds and runs the unit tests on cygwin with each new patch that we commit. Regards, Zooko The Tahoe-LAFS team is pleased to announce the immediate availab

"more reliable pipes" in 1.7

. I have a problem with pipes (stdin/stdout in a subprocess) [1] which I haven't been able to narrow down into a minimal test case, and I would like to learn more about the changes that went into that "more reliable pipes". Thanks! Regards, Zooko [1] http://sourcewa

ANNOUNCING Tahoe-LAFS v1.4

Folks: We use cygwin tools quite a lot to build the native-Win32 version of Tahoe-LAFS, and we also maintain a cygwin port. You can see the results of the unit tests on Cygwin on our buildbot. Regards, Zooko ANNOUNCING Tahoe, the Least-Authority Filesystem, v1.4 The allmydata.org team

ANNOUNCING allmydata.org "Tahoe", the Least-Authority Filesystem, v1.3

Folks: We maintain a cygwin buildbot on http://allmydata.org/buildbot so that we're sure this p2p disk-sharing system always passes all tests on cygwin. Please try it out and let us know what you think. Regards, Zooko ANNOUNCING allmydata.org "Tahoe", the Least-Autho

closing stdout in a child python process means that process doesn't receive bytes from stdin anymore.

as well: http://bugs.python.org/issue4295 # closing stdout in a child process on cygwin means that process doesn't receive bytes from stdin anymore. I think. The version of the cygwin package of python is 2.5.1-2. Regards, Zooko --- http://allmydata.org -- Tahoe, the Least-Authorit

ANNOUNCING Allmydata.org "Tahoe", the Least-Authority Filesystem, v1.1

Inc. [13], a provider of consumer backup services. Allmydata, Inc. contributes hardware, software, ideas, bug reports, suggestions, demands, and money (employing several allmydata.org Tahoe hackers and instructing them to spend part of their work time on this free-software project). We are eternal

announcing allmydata.org "Tahoe", the Least-Authority Filesystem, v1.0

cygwin. Regards, Zooko ANNOUNCING Allmydata.org "Tahoe", the Least-Authority Filesystem, v1.0 We are pleased to announce the release of version 1.0 of the "Tahoe" Least Authority Filesystem. The "Tahoe" Least Authority Filesystem is a secure, decentralized, fault-to

announcing allmydata.org "Tahoe" v0.9

llowing them to spend part of their work time on the next-generation, free-software project). We are eternally grateful! Zooko O'Whielacronx on behalf of the allmydata.org team March 13, 2008 Boulder, Colorado, USA [1] http://allmydata.org/trac/tahoe/browser/relnotes.txt?rev=2183 [2] http://al

announcing allmydata.org "Tahoe" v0.8

false which, like all supported platforms, should always be green to show that all unit tests pass. Please try it out and report any problems to [EMAIL PROTECTED] Regards, Zooko ANNOUNCING: Allmydata.org "Tahoe" version 0.8 We are pleased to announce the release of version 0.8 o

Re: how to run "make check" (bug in FAQ)

of /oss/src, as earlier posted. Could that be causing this make check to hang? Can I recover from that more efficiently than doing a full fresh CVS checkout? Thanks for your help. Regards, Zooko -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem report

Re: how to run "make check" (bug in FAQ)

uot;make check" is now running on my system. Regards, Zooko -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

how to run "make check" (bug in FAQ)

with > make [1]: *** No rule to make target '/oss/src/winsup/w32api/lib/ libkernel32.a', needed by `cygwin0.dll'. Stop. I don't immediately see how to build that lib, and it is also apparent that I've left the beaten track, so I'm submitting this e-

Re: failed to build from source

of configury error that it would try to link against -liconv if required libs are missing. This is the problem to which I wanted to draw attention. Regards, Zooko -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html

failed to build from source

unhandled argument `/usr/lib/libiconv.la' make[4]: *** [size.exe] Error 1 make[4]: Leaving directory `/cygdrive/c/playground/cygwin/build/ binutils' --- Regards, Zooko -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/p

Re: how to build cygwin using itself

omething is wrong with your cvs client configuration. Thanks again for your help, Brian. I ran "cvs co winsup" again, and this time I did get newlib. I don't know what I did wrong last time. I'm sorry for the confusion. Regards, Zooko -- Unsubscribe info: http://cyg

Re: how to build cygwin using itself

On Jul 27, 2007, at 11:43 AM, Brian Dessent wrote: zooko wrote: http://cygwin.com/cvs.html Which say to check out "winsup". That's your problem. I'm not sure why that page says that, but just checking out winsup will give you a tree that can't be used to build

how to build cygwin using itself

from ../../../../../src/newlib/libc/posix/execvp.c:9: /c/playground/cygwin/src/newlib/libc/include/sys/dirent.h:10:2: #error " not supported" --- Could someone give me a hint as to what other steps are necessary to build cygwin using itself? Thanks! Regards,