Re: Add retry logic to rebaseall

2014-01-15 Thread Christopher Faylor
On Wed, Jan 15, 2014 at 11:23:08PM -0500, David Boyce wrote: >Jason et al, > >Here's a suggested new flag (with patch, attached) for >/usr/bin/rebaseall. It adds a -w(ait) flag which causes the check for >running Cygwin processes to be done in a loop, breaking out and doing >the rebaseall as soon a

RE: Extended attributes

2014-01-15 Thread Pavel Fedin
Hello! > > What do you think about adding other possible namespaces (system, > > security, and... don't remember the 3rd one) ? So that when > > manipulating UNIX archives etc these attributes could be kept along > > with files ? At least we have one use case now. > > That doesn't make sense.

cyrus-sasl: missing sys/types.h

2014-01-15 Thread Yaakov (Cygwin/X)
David, There is an issue with stock cyrus-sasl compiling kdepimlibs on all platforms: https://bugzilla.redhat.com/show_bug.cgi?id=906519 Could you add the patch there to your package? Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/

Re: fork() + file descriptor bug in 1.7.27(0.271/5/3) 2013-12-09 11:54

2014-01-15 Thread tednolan
In message <20140115163354.ga30...@calimero.vinschen.de>you write: >--ew6BAiZeqk4r7MaW >Content-Type: text/plain; charset=utf-8 >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Jan 15 10:28, tedno...@bellsouth.net wrote: >> In message <52d63ce2.9060...@lysator.liu.se>

Add retry logic to rebaseall

2014-01-15 Thread David Boyce
Jason et al, Here's a suggested new flag (with patch, attached) for /usr/bin/rebaseall. It adds a -w(ait) flag which causes the check for running Cygwin processes to be done in a loop, breaking out and doing the rebaseall as soon as it finds a quiescent moment. We run Cygwin on build servers whic

[ANNOUNCEMENT] Updated: Cygwin 32<->64 cross-toolchains

2014-01-15 Thread Yaakov (Cygwin/X)
The following packages has been updated for the Cygwin x86 distribution: * cygwin64-1.7.27-1 * cygwin64-gcc-ada-4.8.2-1 (NEW) * cygwin64-gcc-core-4.8.2-1 * cygwin64-gcc-fortran-4.8.2-1 * cygwin64-gcc-g++-4.8.2-1 * cygwin64-gcc-objc-4.8.2-1 * cygwin64-gcc-objc++-4.8.2-1 * cygwin64-w32api-headers-3

[ANNOUNCEMENT] Updated: poppler-0.22.5-2

2014-01-15 Thread Yaakov (Cygwin/X)
The following packages have been updated for both arches: * poppler-0.22.5-2 * libpoppler37-0.22.5-2 * libpoppler-devel-0.22.5-2 * libpoppler-cpp0-0.22.5-2 * libpoppler-cpp-devel-0.22.5-2 * libpoppler-glib8-0.22.5-2 * libpoppler-glib-devel-0.22.5-2 * libpoppler-qt4_4-0.22.5-2 * libpoppler-qt4-dev

[ANNOUNCEMENT] New: mcpp-2.7.2-1

2014-01-15 Thread Yaakov (Cygwin/X)
The following packages has been added to the Cygwin distribution: * mcpp-2.7.2-1 * libmcpp0-2.7.2-1 * libmcpp-devel-2.7.2-1 mcpp is a C/C++ preprocessor with the highest conformance which implements C90, C99 and C++98. mcpp has plentiful diagnostics and many pragmas. It is useful to check po

Re: Problem w/ gcc: error: spawn: No such file or directory; cygcheck.out attached.

2014-01-15 Thread Linda Walsh
Mark Geisert wrote: There was some discussion recently, --- *Thanks*... at least I know where to report the bug (in gcc): on linux -- did a similar test -- mounted /usr/bin on /bin and changed my path to have /bin first: Ishtar:law/bin> PATH=/bin:$PATH Ishtar:law/bin> gcc hello.c gcc: error t

Re: unable to run any cygwin commands: error while loading shared libraries: C

2014-01-15 Thread Larry Hall (Cygwin)
On 1/15/2014 10:11 AM, Mateusz Malinowski wrote: Hello, I have a problem similar to one described in "error while loading shared libraries: ?: cannot open shared object file: No such file or directory" thread, though in my case I can't run any cygwin commands (i.e. I can't even open cygwin's bas

Re: Problem w/ gcc: sensitive to path it was invoked on...

2014-01-15 Thread Larry Hall (Cygwin)
On 1/15/2014 4:28 PM, Linda Walsh wrote: gcc is sensitive to the path it was invoked on?... gcc bug? Jon already addressed this: -- Larry _ A: Yes. > Q: Are you sure? >

Re: Problem w/ gcc: sensitive to path it was invoked on...

2014-01-15 Thread Linda Walsh
Mark Geisert wrote: Linda Walsh writes: > Can't believe doesn't work for anyone. > > For me, I've tried multiple c progs (simple ones), You don't supply any example that shows your attempt and the resulting error message(s). So maybe it (whatever *it* is) is working for everybody else? U

Re: Install packages without documentation

2014-01-15 Thread Larry Hall (Cygwin)
On 1/15/2014 6:45 AM, BGINFO4X wrote: Hello everybody, I'm trying to build a "small release" ... Normally /usr/share contains at least 50MB: folders like "doc", "man", "info", ... Is there any way to install cygwin packages without the documentation ? No, not really. Observe: $ cygcheck -f

Re: fork() + file descriptor bug in 1.7.27(0.271/5/3) 2013-12-09 11:54

2014-01-15 Thread Corinna Vinschen
On Jan 15 11:39, Tom Honermann wrote: > On 01/13/2014 11:06 AM, tedno...@bellsouth.net wrote: > ... > > switch (fork()) { > > > > /* error */ > > case -1: > ... > > /* child */ > > case

Re: fork() + file descriptor bug in 1.7.27(0.271/5/3) 2013-12-09 11:54

2014-01-15 Thread Tom Honermann
On 01/13/2014 11:06 AM, tedno...@bellsouth.net wrote: ... switch (fork()) { /* error */ case -1: ... /* child */ case 0: fprin

Re: fork() + file descriptor bug in 1.7.27(0.271/5/3) 2013-12-09 11:54

2014-01-15 Thread Corinna Vinschen
On Jan 15 10:28, tedno...@bellsouth.net wrote: > In message <52d63ce2.9060...@lysator.liu.se>you write: > >On 2014-01-15 05:53, Lord Laraby wrote: > >> On Tue, Jan 14, 2014 at 10:50 AM, Ted Nolan wrote: > >>> In message <52d55d96.8070...@redhat.com> you write: > > Your program may be viol

Re: fork() + file descriptor bug in 1.7.27(0.271/5/3) 2013-12-09 11:54

2014-01-15 Thread tednolan
In message <52d63ce2.9060...@lysator.liu.se>you write: >On 2014-01-15 05:53, Lord Laraby wrote: >> On Tue, Jan 14, 2014 at 10:50 AM, Ted Nolan wrote: >>> In message <52d55d96.8070...@redhat.com> you write: Your program may be violating POSIX, which would trigger undefined behavio >r.

unable to run any cygwin commands: error while loading shared libraries: C

2014-01-15 Thread Mateusz Malinowski
Hello, I have a problem similar to one described in "error while loading shared libraries: ?: cannot open shared object file: No such file or directory" thread, though in my case I can't run any cygwin commands (i.e. I can't even open cygwin's bash). I am aware that in that thread the problem was

Install packages without documentation

2014-01-15 Thread BGINFO4X
Hello everybody, I'm trying to build a "small release" ... Normally /usr/share contains at least 50MB: folders like "doc", "man", "info", ... Is there any way to install cygwin packages without the documentation ? There are any drawbacks? Thanks a lot for your time. Regards. -- Problem reports

Re: Maintainer for git?

2014-01-15 Thread Adam Dinwoodie
On Sun, Jan 12, 2014 at 01:33:17PM +, Adam Dinwoodie wrote: > On 12 January 2014 02:58, Steven Penny wrote: > > On Sat, Jan 11, 2014 at 5:52 PM, Adam Dinwoodie wrote > >> [my build]: http://tastycake.net/~adam/cygwin/ > > > > Sorry, no dice > > > > # git --version > > git version 1.8.5.2 > > >

Re: Extended attributes

2014-01-15 Thread Corinna Vinschen
On Jan 15 10:27, Pavel Fedin wrote: > Hello! > > > "user." xattrs are supported, but no others. This is partially to have > > smooth support of xattrs when using Samba shares. See the attr > > package and the getxattr, etc. calls in Cygwin's ntea.cc. > > Yes, i have checked that. > What do

g++: is missing C++11 functions

2014-01-15 Thread Achille Fouilleul
Hi, On cygwin64, g++ -std=c++11 fails to compile simple programs like this one: #include #include int main() { std::printf("%d\n", (int)std::lround(1.23)); return 0; } rr.cpp: In function ‘int main()’: rr.cpp:6:28: error: ‘lround’ is not a member of ‘std’ std::printf("%d\n", (int)std::

Re: Problem w/ gcc: error: spawn: No such file or directory; cygcheck.out attached.

2014-01-15 Thread Mark Geisert
Linda Walsh writes: > Can't believe doesn't work for anyone. > > For me, I've tried multiple c progs (simple ones), > same thing. > > Ideas? You don't supply any example that shows your attempt and the resulting error message(s). So maybe it (whatever *it* is) is working for everybody else? >