Re: relationship between Cygwin and Redhat / Fedora packages?

[Brian Inglis]

On 2017-06-22 18:12, Lloyd Wood via cygwin wrote:
> What is the relationship between Cygwin packages and Red Hat rpms at this
> point?

I don't think you can say much about any relationship - most Cygwin packages are
likely to be more current than RHEL releases, some more current than stable
Fedora releases but behind Rawhide releases, some Fedora releases are more
current than Cygwin releases, some may be behind: you would have to cross check
each Cygwin package release against available RPMs.

> If something gets picked up for Cygwin, is it likely to make its way into
> e.g. Fedora, or vice versa?
If something gets picked up for Cygwin, it is likely to be available in Debian,
Fedora, and other Linux distros.
Cygwin depends on utilities and their library dependencies being portable to
non-Unix systems, and not dependent on Linux or Unix features which are either
not available in Windows, or not accessible by a Windows user.

That says nothing about which has the more current releases, as each package
maintainer makes their own calls about when a release is stable under each
distro, and each distro has their own rules about when they make releases; major
Linux distros have more maintainers than Cygwin, and some of them may be full
time positions, whereas Cygwin has only volunteers.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

git-2.12.3-1: Cannot push to a remote with a Windows network path URL

[Jonathan Chan]

After updating to git-2.12.3-1, I have been unable to push to a remote
with a Windows network path URL:
$ git push origin
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 273 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 1 (delta 0)
remote: error: object directory
/network/path/to/git-repository/objects does not exist; check
.git/objects/info/alternates.
remote: fatal: unresolved deltas left after unpacking
error: remote unpack failed: unpack-objects abnormal exit
To file:network/path/to/git-repository
  ! [remote rejected]   master -> master (unpacker error)
error: failed to push some refs to 'file:network/path/to/git-repository'

Notes:
- Fetching works
- Pushing works if I use EGit (in Eclipse)
- Pushing works if I change the remote URL to use a drive mapped to
the network path

Additional searching turned up Issue #979 on git-for-windows:
https://github.com/git-for-windows/git/issues/979

Issue #979 appears to have been fixed in git and included in
2.11.1..2.13.1 releases:
https://github.com/git/git/commit/7814fbe3f1e7cea1a675408df7b5dd1f5be731cc

I did not encounter this behavior prior to git-2.12.2-1. This is for x86_64.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[Andrey Repin]

Greetings, Wouter van Doorn!

> On 22 June 2017 at 15:08, René Berber wrote:
>> On 6/22/2017 8:13 AM, Wouter van Doorn wrote:
>>
>> [snip]
>>> STOP PRESS: in gdb, the output IS there:
>>> User-PC-> gdb hello.exe
>>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
>> ...
>>> Reading symbols from hello.exe...done.
>>> (gdb) run
>>> Starting program: /home/User/c_dir/hello.exe
>>> [New Thread 6868.0x5b0]
>>> [New Thread 6868.0x18dc]
>>> [New Thread 6868.0x1990]
>>> Hello, world!
>>> [Thread 6868.0x1990 exited with code 0]
>>> [Inferior 1 (process 6868) exited normally]
>>> (gdb)
>>>
>>> Which is dandy, but then why, outside of gdb, is there nothing at all?
>>
>> What is "outside"?
>>
>> Are you running this from mintty (recommended) or the Cygwin.bat cmd window?
>>
>> Which shell? (i.e. echo $SHELL)

> With 'outside', I meant a normal run not involving gdb at all. Sorry
> if I was unclear.

> Yes, it's minty, and it's /bin/bash.

> Out of desperation, I have added a sleep for two seconds both before
> and after the printf statement. The sleep does not happen either! The
> prompt is immediately back, so it's more than just 'no output', it
> seems my code never even gets started. Does this shed any new light?


Did you try to rebase your program?

P.S.
And did you try to not top-post in this list? Thank you in advance.


-- 
With best regards,
Andrey Repin
Friday, June 23, 2017 03:48:14

Sorry for my terrible english...

Request new nasm package

[Steven Penny]

Please update the NASM (Netwide Assembler) package. Current version is:

   2.10.07 (Jan 2013)

x264 now requires at least:

   2.13 (Apr 2017)

References:

- http://github.com/cygwinports/nasm
- http://github.com/mirror/x264/commit/d2b5f48
- http://nasm.us/pub/nasm/releasebuilds


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

relationship between Cygwin and Redhat / Fedora packages?

[Lloyd Wood via cygwin]

What is the relationship between Cygwin packages and
Red Hat rpms at this point?

If something gets picked up for Cygwin, is it likely
to make its way into e.g. Fedora, or vice versa?

thanks
 
Lloyd Wood
http://savi.sf.net/

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[Thomas Wolff]

Am 22.06.2017 um 15:13 schrieb Wouter van Doorn:

Hi René,

Thanks for your attempts at having me dig deeper. So far, I am not
striking lucky. Here's the various outputs, that don't say anything
obvious to me:
User-PC-> echo $PATH
/home/User/exe.CYGWIN:/home/User/bin:/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:...
Do you have any of make, cc or gcc in /home/Usr/exe.CYGWIN or 
/home/User/bin ?

What does `type make` and `type cc` / `type gcc` say?


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

libuv uv__io_poll or uv__poll_io R tolerance, giving me uv polio, help?

[Ian Lambert via cygwin]

Can someone please help with getting libuv to compile, as part of:

$ R CMD /usr/lib/R/bin/INSTALL -l /usr/lib/R/site-library  
httpuv_1.3.3[mod].tar.gz

I think I may have stumbled across a bug in the libuv core.c and/or internal.h
source, but I'm not sure. From a search of the maillist, I know libuv may not
be fully compatible, but why not try...

https://cygwin.com/ml/cygwin/2015-12/msg00023.html
https://sourceware.org/ml/cygwin/2016-08/msg00322.html

Goal: Install and run R tolerance package on cygwin (or windos).

Roadblocks: 
Corporate approved windos R, version 3.1.1 (2014-07-10) -- "Sock it to Me":
   Will not install tolerance package, Error: This is R 3.1.1, package 
‘tolerance’ needs >= 3.2.0
Newer downloaded windos R, version 3.4.0 (2017-04-21) -- "You Stupid Darkness"
   Cannot access internet within R (proxy issues as always), so it requires
   downloading and individually installing and loading about 2 dozen other 
   prerequisite packages supporting tolerance. This may be the fall-back.

More details:

In Cygwin, CYGWIN_NT-6.1   2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin

$ R --version
R version 3.4.0 (2017-04-21) -- "You Stupid Darkness"

So, like a good (or bad) cygwin soldier, I've downloaded and done the install
as in the R CMD command above, for the following packages:

config/
crayon/
digest/
evaluate/
highr/
htmltools/
htmlwidgets/
jsonlite/
knitr/
magrittr/
markdown/
mime/
praise/
R6/
Rcpp/
sourcetools/
stringi/
stringr/
testthat/
xtable/
yaml/

However, this still leaves tolerance, which needs rgl, which needs shiny, 
which needs hpuv, and this is where I am stuck.

$ R CMD /usr/lib/R/bin/INSTALL -l /usr/lib/R/site-library  
tolerance_1.3.0.tar.gz 
ERROR: dependency ‘rgl’ is not available for package ‘tolerance’

$ R CMD /usr/lib/R/bin/INSTALL -l /usr/lib/R/site-library rgl_0.98.1.tar.gz 
ERROR: dependency ‘shiny’ is not available for package ‘rgl’

$ R CMD /usr/lib/R/bin/INSTALL -l /usr/lib/R/site-library  shiny_1.0.3.tar.gz 
ERROR: dependency ‘httpuv’ is not available for package ‘shiny’


So.

$ R CMD /usr/lib/R/bin/INSTALL -l /usr/lib/R/site-library  httpuv_1.3.3

gcc -D_GNU_SOURCE 
-I/tmp/Rtmp5WsS2T/R.INSTALL2214f28b836/httpuv/src/libuv/include -
I/tmp/Rtmp5WsS2T/R.INSTALL2214f28b836/httpuv/src/libuv/include/uv-private -
I/tmp/Rtmp5WsS2T/R.INSTALL2214f28b836/httpuv/src/libuv/src -D_LARGEFILE_SOURCE -
D_FILE_OFFSET_BITS=64 -ggdb -O2 -pipe -Wimplicit-function-declaration 
-std=gnu99 -fdebug-
prefix-map=/cygdrive/e/cyg_pub/devel/R/R-3.4.0-1.x86_64/build=/usr/src/debug/R-3.4.0-1
 -
fdebug-prefix-map=/cygdrive/e/cyg_pub/devel/R/R-3.4.0-1.x86_64/src/R-3.4.0=/usr/src/debug/R-
3.4.0-1   -c src/unix/core.c -o src/unix/core.o
src/unix/core.c: In function ‘uv_run’:
src/unix/core.c:317:5: warning: implicit declaration of function ‘uv__poll_io’ 
[-Wimplicit-

function-declaration]
 uv__poll_io(loop, timeout);
 ^


Looking at the source, it seems there may be confusion on ordering of poll and 
io,
or I don't understand the need for both uv__poll_io and uv__io_poll, but 
something 
is wrong, and both are currently used:


$ grep -i uv__poll_io *
poll.c:static void uv__poll_io(uv_loop_t* loop, uv__io_t* w, unsigned int 
events) {
poll.c:  uv__io_init(>io_watcher, uv__poll_io, fd);

$ grep -i uv__io_poll *
core.c:uv__io_poll(loop, timeout);
internal.h:void uv__io_poll(uv_loop_t* loop, int timeout); /* in milliseconds 
or -1 */
kqueue.c:void uv__io_poll(uv_loop_t* loop, int timeout) {
linux-core.c:void uv__io_poll(uv_loop_t* loop, int timeout) {
sunos.c:void uv__io_poll(uv_loop_t* loop, int timeout) {


So, I've tried 2 changes, changing uv__io_poll to uv__poll_io, but neither has 
fixed it:


$ diff core.c /tmp/2nd/httpuv/src/libuv/src/unix/core.c
317c317
< uv__io_poll(loop, timeout);
---
> uv__poll_io(loop, timeout);


$ diff core.c /tmp/3rd/httpuv/src/libuv/src/unix/core.c
317c317
< uv__io_poll(loop, timeout);
---
> uv__poll_io(loop, timeout);


$ diff internal.h /tmp/3rd/httpuv/src/libuv/src/unix/internal.h 
127c127
< void uv__io_poll(uv_loop_t* loop, int timeout); /* in milliseconds or -1 */
---
> void uv__poll_io(uv_loop_t* loop, int timeout); /* in milliseconds or -1 */



and the latest error is as follows:


$ R CMD /usr/lib/R/bin/INSTALL -l /usr/lib/R/site-library  httpuv_1.3.3y.tar.gz

gcc -D_GNU_SOURCE 
-I/tmp/RtmpQa0A69/R.INSTALL2b94587184b0/httpuv/src/libuv/include 
-I/tmp/RtmpQa0A69/R.INSTALL2b94587184b0/httpuv/src/libuv/include/uv-private 
-I/tmp/RtmpQa0A69/R.INSTALL2b94587184b0/httpuv/src/libuv/src 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -ggdb -O2 -pipe 
-Wimplicit-function-declaration -std=gnu99 
-fdebug-prefix-map=/cygdrive/e/cyg_pub/devel/R/R-3.4.0-1.x86_64/build=/usr/src/debug/R-3.4.0-1
 
-fdebug-prefix-map=/cygdrive/e/cyg_pub/devel/R/R-3.4.0-1.x86_64/src/R-3.4.0=/usr/src/debug/R-3.4.0-1
   -c src/unix/poll.c -o src/unix/poll.o
src/unix/poll.c:30:13: error: conflicting types for ‘uv__poll_io’
 static void uv__poll_io(uv_loop_t* 

Re: rxvt won't stay running

[Mike Brown]

On Thu, Jun 22, 2017 at 09:12:45AM -0500, Ren?? Berber wrote:
> On 6/22/2017 4:45 AM, Mike Brown wrote:
> 
> > I've installed the latest (as of this writing) Cygwin base and a few other
> > packages.
> [snip]
> > Any ideas why it is failing?  Something you need me to look at?  It isn't
> > anything in the home files that I copied over from the XP box, because 
> > before
> > I did that, I tried starting and it flashed and died.
> 
> A long time ago rxvt changed from supporting Windows (native) to only
> working under X-Windows (a.k.a. Cygwin/X or equivalent).

Ah, so in a galaxy far, far, away, it just might work. :-)

Thanks for the reason it no longer works.

MB
-- 
e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII
6082066...@email.uscc.net (140 char limit)   \ / Ribbon Campaign
Visit - URL: http://vidiot.com/   X  Against
 http://vidiot.net/  / \ HTML Email
"You're Sherlock Holmes, wear the damn hat!" - Watson to Sherlock
Sherlock - The Abominable Bride - 1/01/16

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: rxvt won't stay running

[Mike Brown]

On Thu, Jun 22, 2017 at 09:48:43AM -0400, cyg Simple wrote:
> On 6/22/2017 5:45 AM, Mike Brown wrote:
> > I've installed the latest (as of this writing) Cygwin base and a few other
> > packages.
> > 
> 
> You don't say if it was 32 or 64 bit. But ...

Sorry, 64bit.

> > I have a startup batch file on my XP box that I copied over to the new Win7
> > box (modifying the HOME variable to match the new box).
> > 
> > I also copied over the home directory from the XP box, so that I can get the
> > .z* setup files and scripts that I have in my bin directory.
> > 
> > But, when I run it, it just flashes and dies.
> > 
> > Here is the contents:
> > ==
> > @echo off
> > 
> > 
> > C:
> > chdir C:\cygwin\bin
> > set HOME=\cygwin\home\Brown
> > 
> > rxvt -e /bin/zsh --login -i
> > ==
> > 
> > Any ideas why it is failing?  Something you need me to look at?  It isn't
> > anything in the home files that I copied over from the XP box, because 
> > before
> > I did that, I tried starting and it flashed and died.
> > 
> 
> Simply, it isn't supported any longer.  Use mintty instead which should
> have been installed if you actually used setup.exe to install Cygwin.
> If not, start over and use it.

Yep, it put a shortcut on the desktop.  I run zsh, not bash.  Since rxvt
is no longer viable, I went digging into the properties and help for mintty
and added what was needed to start zsh.

All is well now.

MB
-- 
e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII
6082066...@email.uscc.net (140 char limit)   \ / Ribbon Campaign
Visit - URL: http://vidiot.com/   X  Against
 http://vidiot.net/  / \ HTML Email
"You're Sherlock Holmes, wear the damn hat!" - Watson to Sherlock
Sherlock - The Abominable Bride - 1/01/16

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[Wouter van Doorn]

Well, it's the same antivirus (comodo) that I earlier had a working
system with, and there's also the matter of it running fine under a
windows command prompt.

Thanks for all your suggestions!

On 22 June 2017 at 17:18, René Berber  wrote:
> On 6/22/2017 10:59 AM, Wouter van Doorn wrote:
>
>> With 'outside', I meant a normal run not involving gdb at all. Sorry
>> if I was unclear.
>>
>> Yes, it's minty, and it's /bin/bash.
>>
>> Out of desperation, I have added a sleep for two seconds both before
>> and after the printf statement. The sleep does not happen either! The
>> prompt is immediately back, so it's more than just 'no output', it
>> seems my code never even gets started. Does this shed any new light?
>
> Then its down to the 'weird' stuff, any anti-virus installed? (maybe
> even the name hello.exe could cause an anti-virus to block it).
> --
> R. Berber
>
>
> --
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

RE: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[Soegtrop, Michael]

Dear Wouter,

when things get bizarre on Windows, I tend to use Sysinternals/Microsoft 
ProcMon. It is free and can be downloaded here:

https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx

ProcMon shows you all Windows system calls with parameters and error results. 
You should see the CreatProcess call and possibly can see why it fails. Since 
Cygwin in the end creates a windows process with windows system calls, it 
should also help for Cygwin. In case your process does start and fails during 
initialization, you can also see the Windows system calls it does. If there are 
DLLs missing, you can also see that.

Best regards,

Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[René Berber]

On 6/22/2017 10:59 AM, Wouter van Doorn wrote:

> With 'outside', I meant a normal run not involving gdb at all. Sorry
> if I was unclear.
> 
> Yes, it's minty, and it's /bin/bash.
> 
> Out of desperation, I have added a sleep for two seconds both before
> and after the printf statement. The sleep does not happen either! The
> prompt is immediately back, so it's more than just 'no output', it
> seems my code never even gets started. Does this shed any new light?

Then its down to the 'weird' stuff, any anti-virus installed? (maybe
even the name hello.exe could cause an anti-virus to block it).
-- 
R. Berber


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[Wouter van Doorn]

With 'outside', I meant a normal run not involving gdb at all. Sorry
if I was unclear.

Yes, it's minty, and it's /bin/bash.

Out of desperation, I have added a sleep for two seconds both before
and after the printf statement. The sleep does not happen either! The
prompt is immediately back, so it's more than just 'no output', it
seems my code never even gets started. Does this shed any new light?

On 22 June 2017 at 15:08, René Berber  wrote:
> On 6/22/2017 8:13 AM, Wouter van Doorn wrote:
>
> [snip]
>> STOP PRESS: in gdb, the output IS there:
>> User-PC-> gdb hello.exe
>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
> ...
>> Reading symbols from hello.exe...done.
>> (gdb) run
>> Starting program: /home/User/c_dir/hello.exe
>> [New Thread 6868.0x5b0]
>> [New Thread 6868.0x18dc]
>> [New Thread 6868.0x1990]
>> Hello, world!
>> [Thread 6868.0x1990 exited with code 0]
>> [Inferior 1 (process 6868) exited normally]
>> (gdb)
>>
>> Which is dandy, but then why, outside of gdb, is there nothing at all?
>
> What is "outside"?
>
> Are you running this from mintty (recommended) or the Cygwin.bat cmd window?
>
> Which shell? (i.e. echo $SHELL)
> --
> R. Berber
>
>
> --
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[Wouter van Doorn]

Nice thought, but no, that's not it. The standard utilities behave
normally, only the things I compile myself stay schtumm.

On 22 June 2017 at 14:57, cyg Simple  wrote:
>>
>> STOP PRESS: in gdb, the output IS there:
>> User-PC-> gdb hello.exe
>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "i686-pc-cygwin".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> .
>> Find the GDB manual and other documentation resources online at:
>> .
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from hello.exe...done.
>> (gdb) run
>> Starting program: /home/User/c_dir/hello.exe
>> [New Thread 6868.0x5b0]
>> [New Thread 6868.0x18dc]
>> [New Thread 6868.0x1990]
>> Hello, world!
>> [Thread 6868.0x1990 exited with code 0]
>> [Inferior 1 (process 6868) exited normally]
>> (gdb)
>>
>> Which is dandy, but then why, outside of gdb, is there nothing at all?
>> Still stumped!
>
> Is your prompt overwriting the output of the program?
>
> Try:
>
> $ hello | cat
> $ hello | grep ello
>
> etc.
>
> --
> cyg Simple
>
> --
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

[newlib-cygwin] Update and sort list of cygwin setup command line options.

[Jon TURNEY]

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=f4fb7b93ef1bdfee5db11244d55bee400441a1b6

commit f4fb7b93ef1bdfee5db11244d55bee400441a1b6
Author: Jon Turney 
Date:   Fri May 26 12:23:39 2017 +0100

Update and sort list of cygwin setup command line options.

Diff:
---
 winsup/doc/faq-setup.xml | 62 +---
 1 file changed, 38 insertions(+), 24 deletions(-)

diff --git a/winsup/doc/faq-setup.xml b/winsup/doc/faq-setup.xml
index 0fc2635..3917f2d 100644
--- a/winsup/doc/faq-setup.xml
+++ b/winsup/doc/faq-setup.xml
@@ -53,45 +53,59 @@ For other options, search the mailing lists with terms such 
as
 Does Setup accept command-line arguments?
 
 
-Yes, the full listing is written to the setup.log 
file 
-when you run setup-x86.exe --help or
-setup-x86_64.exe --help. The current options are:
+Yes, run setup-x86.exe --help or
+setup-x86_64.exe --help for a list.
+
+
 
-Command Line Options:
+--allow-unsupported-windowsAllow old, unsupported Windows versions
+ -a --arch architecture to install (x86_64 or x86)
+ -C --categories   Specify entire categories to install
+ -o --delete-orphans   remove orphaned packages
+ -A --disable-buggy-antivirus  Disable known or suspected buggy anti virus
+   software packages during execution.
  -D --download Download from internet
+ -f --force-currentselect the current version for all packages
+ -h --help print help
+ -I --include-source   Automatically include source download
+ -i --ini-basename Use a different basename, e.g. "foo",
+   instead of "setup"
+ -U --keep-untrusted-keys  Use untrusted keys and retain all
  -L --local-installInstall from local directory
- -s --site Download site
- -O --only-siteIgnore all sites except for -s
- -R --root Root installation directory
- -x --remove-packages  Specify packages to uninstall
- -c --remove-categoriesSpecify categories to uninstall
- -P --packages Specify packages to install
- -C --categories   Specify entire categories to install
- -p --proxyHTTP/FTP proxy (host:port)
- -a --arch architecture to install (x86_64 or x86)
- -q --quiet-mode   Unattended setup mode
- -M --package-manager  Semi-attended chooser-only mode
+ -l --local-package-dirLocal package directory
+ -m --mirror-mode  Skip availability check when installing from
+   local directory (requires local directory to
+   be clean mirror!)
  -B --no-admin Do not check for and enforce running as
Administrator
- -h --help print help
- -l --local-package-dirLocal package directory
+ -d --no-desktop   Disable creation of desktop shortcut
  -r --no-replaceonreboot   Disable replacing in-use files on next
reboot.
- -X --no-verifyDon't verify setup.ini signatures
  -n --no-shortcuts Disable creation of desktop and start menu
shortcuts
  -N --no-startmenu Disable creation of start menu shortcut
- -d --no-desktop   Disable creation of desktop shortcut
+ -X --no-verifyDon't verify setup.ini signatures
+ -O --only-siteIgnore all sites except for -s
+ -M --package-manager  Semi-attended chooser-only mode
+ -P --packages Specify packages to install
+ -p --proxyHTTP/FTP proxy (host:port)
+ -Y --prune-installprune the installation to only the requested
+   packages
  -K --pubkey   URL of extra public key file (gpg format)
+ -q --quiet-mode   Unattended setup mode
+ -c --remove-categoriesSpecify categories to uninstall
+ -x --remove-packages  Specify packages to uninstall
+ -R --root Root installation directory
  -S --sexpr-pubkey Extra public key in s-expr format
+ -s --site Download site
  -u --untrusted-keys   Use untrusted keys from last-extrakeys
- -U --keep-untrusted-keys  Use untrusted keys and retain all
  -g --upgrade-also also upgrade installed packages
- -o --delete-orphans   remove orphaned packages
- -A --disable-buggy-antivirus  Disable known or suspected buggy anti virus
-

[newlib-cygwin] Update documentation of cygwin setup proxy configuration details

[Jon TURNEY]

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=95e66aae3328a9aa2d5d992489228088008dad37

commit 95e66aae3328a9aa2d5d992489228088008dad37
Author: Jon Turney 
Date:   Mon Jun 19 17:18:36 2017 +0100

Update documentation of cygwin setup proxy configuration details

Diff:
---
 winsup/doc/setup-net.xml | 13 +
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/winsup/doc/setup-net.xml b/winsup/doc/setup-net.xml
index 211bbed..82b1e0d 100644
--- a/winsup/doc/setup-net.xml
+++ b/winsup/doc/setup-net.xml
@@ -132,14 +132,11 @@ or in case you need to reinstall a package.
 
 Connection Method
 
-The Direct Connection method of downloading will 
-directly download the packages, while the IE5 method will leverage your 
-IE5 cache for performance. If your organisation uses a proxy server or
-auto-configuration scripts, the IE5 method also uses these settings.
-If you have a proxy server, you can manually type it into 
-the Use Proxy section. Unfortunately, 
-setup.exe does not currently support password
-authorization for proxy servers.
+The Direct Connection method of downloading will
+directly connect.  If your system is configured to use a proxy server or
+auto-configuration scripts, the Use System Proxy Settings
+method uses those settings.  Alternatively, you can manually enter proxy
+settings into the Use HTTP/FTP Proxy section.
 
 

[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.8.1-0.1

[Corinna Vinschen]

Hi folks,


I uploaded a new Cygwin test release 2.8.1-0.1

I'm planning for a release next week.  Please test.

===

What's new:
---

- Allow unprivileged symlink creation in Windows 10 1703 and later.

- New API: reallocarray

- New API: strverscmp, versionsort.


What changed:
-

- The XSI form of sigpause, which removes the given signal from the process's
  signal mask, is made available when compiling with _XOPEN_SOURCE or
  _GNU_SOURCE.

Bug Fixes
-

- Fix build problem with GCC 6.
  Addresses: https://cygwin.com/ml/cygwin-patches/2017-q2/msg00014.html

- Fix stat.st_blocks for files compressed with CompactOS method.
  Addresses: https://cygwin.com/ml/cygwin-patches/2017-q2/msg00026.html

- Fix extreme lagging during strace in certain scenarios.
  Addresses: https://cygwin.com/ml/cygwin/2017-04/msg00240.html

- Fix unwanted decimal point localization in /proc/loadavg
  Addresses: Reported on IRC.

- Fix ldd potentially looping on non-continuable exception
  Addresses: https://cygwin.com/ml/cygwin-patches/2017-q2/msg2.html

- Fix buffer overflow problem in wcsxfrm/wcsxfrm_l.
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00149.html

- Fix crash if env var name starts with non-ASCII char
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00330.html

- Fix return value of lrint{f,l} on x86_64 Cygwin.
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00388.html

- Fix native language support in regtool(1).
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00245.html

===


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

TEST RELEASE: Cygwin 2.8.1-0.1

[Corinna Vinschen]

Hi folks,


I uploaded a new Cygwin test release 2.8.1-0.1

I'm planning for a release next week.  Please test.

===

What's new:
---

- Allow unprivileged symlink creation in Windows 10 1703 and later.

- New API: reallocarray

- New API: strverscmp, versionsort.


What changed:
-

- The XSI form of sigpause, which removes the given signal from the process's
  signal mask, is made available when compiling with _XOPEN_SOURCE or
  _GNU_SOURCE.

Bug Fixes
-

- Fix build problem with GCC 6.
  Addresses: https://cygwin.com/ml/cygwin-patches/2017-q2/msg00014.html

- Fix stat.st_blocks for files compressed with CompactOS method.
  Addresses: https://cygwin.com/ml/cygwin-patches/2017-q2/msg00026.html

- Fix extreme lagging during strace in certain scenarios.
  Addresses: https://cygwin.com/ml/cygwin/2017-04/msg00240.html

- Fix unwanted decimal point localization in /proc/loadavg
  Addresses: Reported on IRC.

- Fix ldd potentially looping on non-continuable exception
  Addresses: https://cygwin.com/ml/cygwin-patches/2017-q2/msg2.html

- Fix buffer overflow problem in wcsxfrm/wcsxfrm_l.
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00149.html

- Fix crash if env var name starts with non-ASCII char
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00330.html

- Fix return value of lrint{f,l} on x86_64 Cygwin.
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00388.html

- Fix native language support in regtool(1).
  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00245.html

===


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat

Re: rxvt won't stay running

[René Berber]

On 6/22/2017 4:45 AM, Mike Brown wrote:

> I've installed the latest (as of this writing) Cygwin base and a few other
> packages.
[snip]
> Any ideas why it is failing?  Something you need me to look at?  It isn't
> anything in the home files that I copied over from the XP box, because before
> I did that, I tried starting and it flashed and died.

A long time ago rxvt changed from supporting Windows (native) to only
working under X-Windows (a.k.a. Cygwin/X or equivalent).
-- 
R. Berber


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[René Berber]

On 6/22/2017 8:13 AM, Wouter van Doorn wrote:

[snip]
> STOP PRESS: in gdb, the output IS there:
> User-PC-> gdb hello.exe
> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
...
> Reading symbols from hello.exe...done.
> (gdb) run
> Starting program: /home/User/c_dir/hello.exe
> [New Thread 6868.0x5b0]
> [New Thread 6868.0x18dc]
> [New Thread 6868.0x1990]
> Hello, world!
> [Thread 6868.0x1990 exited with code 0]
> [Inferior 1 (process 6868) exited normally]
> (gdb)
> 
> Which is dandy, but then why, outside of gdb, is there nothing at all?

What is "outside"?

Are you running this from mintty (recommended) or the Cygwin.bat cmd window?

Which shell? (i.e. echo $SHELL)
-- 
R. Berber


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[cyg Simple]

> 
> STOP PRESS: in gdb, the output IS there:
> User-PC-> gdb hello.exe
> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
> Copyright (C) 2015 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-cygwin".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from hello.exe...done.
> (gdb) run
> Starting program: /home/User/c_dir/hello.exe
> [New Thread 6868.0x5b0]
> [New Thread 6868.0x18dc]
> [New Thread 6868.0x1990]
> Hello, world!
> [Thread 6868.0x1990 exited with code 0]
> [Inferior 1 (process 6868) exited normally]
> (gdb)
> 
> Which is dandy, but then why, outside of gdb, is there nothing at all?
> Still stumped!

Is your prompt overwriting the output of the program?

Try:

$ hello | cat
$ hello | grep ello

etc.

-- 
cyg Simple

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: rxvt won't stay running

[cyg Simple]

On 6/22/2017 5:45 AM, Mike Brown wrote:
> I've installed the latest (as of this writing) Cygwin base and a few other
> packages.
> 

You don't say if it was 32 or 64 bit. But ...

> I have a startup batch file on my XP box that I copied over to the new Win7
> box (modifying the HOME variable to match the new box).
> 
> I also copied over the home directory from the XP box, so that I can get the
> .z* setup files and scripts that I have in my bin directory.
> 
> But, when I run it, it just flashes and dies.
> 
> Here is the contents:
> ==
> @echo off
> 
> 
> C:
> chdir C:\cygwin\bin
> set HOME=\cygwin\home\Brown
> 
> rxvt -e /bin/zsh --login -i
> ==
> 
> Any ideas why it is failing?  Something you need me to look at?  It isn't
> anything in the home files that I copied over from the XP box, because before
> I did that, I tried starting and it flashed and died.
> 

Simply, it isn't supported any longer.  Use mintty instead which should
have been installed if you actually used setup.exe to install Cygwin.
If not, start over and use it.

-- 
cyg Simple

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd

[Wouter van Doorn]

Hi René,

Thanks for your attempts at having me dig deeper. So far, I am not
striking lucky. Here's the various outputs, that don't say anything
obvious to me:
User-PC-> echo $PATH
/home/User/exe.CYGWIN:/home/User/bin:/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Program
Files/Dell/DW WLAN
Card:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program
Files/WIDCOMM/Bluetooth Software:/cygdrive/c/Program
Files/WIDCOMM/Bluetooth Software/syswow64:/cygdrive/c/Program
Files/Git/cmd:/usr/bin:.:/cygrive/c/cygwin/bin:/cygdrive/c/cygwin/bin

===>so yes, /usr/bin is there.

User-PC-> ldd hello.exe
ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x7772)
kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x768b)
KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll
(0x7723)
cygwin1.dll => /usr/bin/cygwin1.dll (0x6100)

===>no missing items

User-PC-> file hello.exe
hello.exe: PE32 executable (console) Intel 80386, for MS Windows

===>nothing here that worries me either.

Any other thoughts?

No doubt overdone, but here's the code:
User-PC-> cat hello.c
#include 

int main(int arg, char **argv) {
printf("Hello, world!\n");
}

and compilation was just by make hello... The simplest thing ever,
you'd say... The only real clue as far as I can see is the exception
in the last line but one of the strace output. But I don't know how to
read that.

STOP PRESS: in gdb, the output IS there:
User-PC-> gdb hello.exe
GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from hello.exe...done.
(gdb) run
Starting program: /home/User/c_dir/hello.exe
[New Thread 6868.0x5b0]
[New Thread 6868.0x18dc]
[New Thread 6868.0x1990]
Hello, world!
[Thread 6868.0x1990 exited with code 0]
[Inferior 1 (process 6868) exited normally]
(gdb)

Which is dandy, but then why, outside of gdb, is there nothing at all?
Still stumped!

Wouter

On 21 June 2017 at 22:48, René Berber  wrote:
> On 6/21/2017 4:10 PM, Wouter van Doorn wrote:
>
>> Having installed Cygwin with no errors I could see, I went on to
>> compile and run "hello world" - as you do. I could make it go from a
>> windows command prompt after modifying the system path to include
>> cygwin\bin, so - so far so good.
>>
>> From the cygwin terminal, however, the same executable refuses to play
>> ball. No text is shown; the command prompt returns instantly.
> [snip]
>
> It could be the program itself, i.e. not coded for a Posix environment,
> or it could be your PATH which should include /usr/bin (as shown, not as
> a Windows path C:\...)
>
> Easiest way to figure it out is by running:
>
> $ ldd hello (or whatever the name of your executable is)
> (sample output)
> ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffaf660)
> ??? => ??? (0x7779)
> wow64.dll => /cygdrive/c/WINDOWS/System32/wow64.dll (0x5aa4)
> wow64win.dll => /cygdrive/c/WINDOWS/System32/wow64win.dll
> (0x5aaa)
>
> In this case the missing cygwin1.dll doesn't even show its name, it
> happens to be the 32-bit version, because I ran ldd from a 64-bit Cygwin
> on a 32-bit Cygwin program, my PATH doesn't include the cygwin 32-bit
> binary directory.
>
> And if that doesn't show the missing libraries, then even
>
> $ file hello
>
> could show a clue, like "PE32+ executable (GUI) x86-64 (stripped to
> external PDB), for MS Windows" which is a GUI program compiled with
> MinGW, i.e. doesn't depend on Cygwin.  Cygwin is not mentioned in the
> output of file, even a Cygwin console program shows something like "PE32
> executable (console) Intel 80386, for MS Windows" or "PE32+ executable
> (console) x86-64, for MS Windows".
>
> Hope this helps.
> --
> R. Berber
>
>
> --
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  

[newlib-cygwin] Note regtool fix in release message

[Corinna Vinschen]

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=92fc6ea7e3141291216564dab36677ab56c9a537

commit 92fc6ea7e3141291216564dab36677ab56c9a537
Author: Corinna Vinschen 
Date:   Thu Jun 22 14:48:43 2017 +0200

Note regtool fix in release message

Signed-off-by: Corinna Vinschen 

Diff:
---
 winsup/cygwin/release/2.8.1 | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/winsup/cygwin/release/2.8.1 b/winsup/cygwin/release/2.8.1
index d03f296..7a5b15f 100644
--- a/winsup/cygwin/release/2.8.1
+++ b/winsup/cygwin/release/2.8.1
@@ -41,3 +41,6 @@ Bug Fixes
 
 - Fix return value of lrint{f,l} on x86_64 Cygwin.
   Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00388.html
+
+- Fix native language support in regtool(1).
+  Addresses: https://cygwin.com/ml/cygwin/2017-05/msg00245.html

rxvt won't stay running

[Mike Brown]

I've installed the latest (as of this writing) Cygwin base and a few other
packages.

I have a startup batch file on my XP box that I copied over to the new Win7
box (modifying the HOME variable to match the new box).

I also copied over the home directory from the XP box, so that I can get the
.z* setup files and scripts that I have in my bin directory.

But, when I run it, it just flashes and dies.

Here is the contents:
==
@echo off


C:
chdir C:\cygwin\bin
set HOME=\cygwin\home\Brown

rxvt -e /bin/zsh --login -i
==

Any ideas why it is failing?  Something you need me to look at?  It isn't
anything in the home files that I copied over from the XP box, because before
I did that, I tried starting and it flashed and died.

MB
-- 
e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII
6082066...@email.uscc.net (140 char limit)   \ / Ribbon Campaign
Visit - URL: http://vidiot.com/   X  Against
 http://vidiot.net/  / \ HTML Email
"You're Sherlock Holmes, wear the damn hat!" - Watson to Sherlock
Sherlock - The Abominable Bride - 1/01/16

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple