Hey Folks,
Trying to track down why our builds started failing after upgrading to cygwin
3.3.3.
Narrowed it down to a change in how make (gmake) is invoked with a specified
directory to execute in and that directory is a network drive in windows (10,
21H2).
simple Makefile attached and
On 2/24/2017 9:43 AM, Eric Blake wrote:
On 02/23/2017 10:57 PM, Steven Penny wrote:
Or more likely, many people likely have pre-existing scripts wrongly
written as #!/bin/sh but which use bash-ism rather than portable
POSIX-specified shell
However, I think it is worth the trouble.
If
On 2/7/2017 9:40 AM, cyg Simple wrote:
On 2/7/2017 9:23 AM, Lee Dilkie wrote:
Cyg, I understand list etiquette but I'm referring to *human* etiquette.
Steve asked for help, got help but rather than acknowledge it (and add a
note at the bottom to *politely* tell Vince that he should find
On 2/7/2017 9:11 AM, cyg Simple wrote:
On 2/6/2017 12:43 PM, Lee Dilkie wrote:
On 2/5/2017 3:59 PM, Steven Penny wrote:
On Sun, 5 Feb 2017 14:12:04, Vince Rice wrote:
On Feb 5, 2017, at 1:53 PM, Steven Penny wrote:
Please fix your email client. You should not be quoting people’s email
On 2/5/2017 3:59 PM, Steven Penny wrote:
On Sun, 5 Feb 2017 14:12:04, Vince Rice wrote:
On Feb 5, 2017, at 1:53 PM, Steven Penny wrote:
Please fix your email client. You should not be quoting people’s email directly.
that's just silly. Anyone with access to this public list has your
On 12/1/2016 5:51 AM, Roberto Ríos Gallardo wrote:
Please give the installers more meaningful names. In particular, make
sure "cygwin" is part of it. "setup-x86_64.exe" is not very obvious. A
version number would be nice too.
I'd agree that adding "cygwin" to the setup program would be nice
On 8/26/2016 9:08 AM, Nellis, Kenneth wrote:
Dear Cygwin Community,
$ ls -l
total 60
-rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe
$ ./hello
Hello, world!
$ cygpath -w hello
hello
$
The purpose of cygpath -w, it seems to me, is to provide
to Windows a valid path given a
On 6/23/2016 6:54 AM, Steven Bardwell wrote:
Here is a "program" that shows the issue I am worried about. It is so simple
that I must be overlooking something really obvious:
#include
#undef FD_SETSIZE
#define FD_SETSIZE 256
#include
#include
main()
{
fd_set rfds;
Corinna Vinschen wrote:
On Nov 10 16:06, Lee Dilkie wrote:
Hi folks,
If this isn't the list, or the method, how would one go about reporting
a bug in the cygpath utility. It is reporting an absolute path for
windows style in all invocations and ignoring the absence of -a.
$ cygpath
Christopher Faylor wrote:
FWIW, it is entirely possible that if you had submitted the requested
cygcheck output the problem would have been more obvious.
--
I don't doubt that for a minute. In fact, I went and gathered all the
cygcheck output and was composing the email when I came
Hi folks,
If this isn't the list, or the method, how would one go about reporting
a bug in the cygpath utility. It is reporting an absolute path for
windows style in all invocations and ignoring the absence of -a.
$ cygpath -w foo
C:\foo
$ cygpath -wa foo
C:\foo
$ cygpath -u foo
foo
$ cygpath
Larry Hall (Cygwin) wrote:
Thanks for the reply Larry.
It is reporting an absolute path for
windows style in all invocations and ignoring the absence of -a.
$ cygpath -w foo
C:\foo
$ cygpath -wa foo
C:\foo
$ cygpath -u foo
foo
$ cygpath -ua foo
/cygdrive/c//foo
WJFFM. What does
Christopher Faylor wrote:
On Mon, Nov 10, 2008 at 06:33:03PM -0500, Lee Dilkie wrote:
Larry Hall (Cygwin) wrote:
Thanks for the reply Larry.
It is reporting an absolute path for
windows style in all invocations and ignoring the absence of -a.
$ cygpath -w foo
C:\foo
Christopher Faylor wrote:
On Mon, Nov 10, 2008 at 11:07:23PM -0500, Lee Dilkie wrote:
Christopher Faylor wrote:
On Mon, Nov 10, 2008 at 06:33:03PM -0500, Lee Dilkie wrote:
Larry Hall (Cygwin) wrote:
Thanks for the reply Larry.
It is reporting
Hi Folks,
I run the setup-1.7 and upgraded my 1.5 version to try it out and I came
across this.
cygwin 1.5
[EMAIL PROTECTED]: /cygdrive/g/dilkiel_Tug_parallel_1/SmallApps/TUG
$ cygpath -m foo
foo
cygwin 1.7
[EMAIL PROTECTED] ~/views/dilkiel_Tug_parallel_1/SmallApps/TUG
$ cygpath -m foo
And on top of that (top posting too), even windows cmd console won't let
you follow .lnk files... They are files, not symlinks. Only explorer
know how to navigate them.
-lee
Brian Dessent wrote:
Gustavo Seabra wrote:
Right, it isn't a directory. But shouldn't Cygwin convert the path and
I found that setting the complier and linker (all the tools, actually)
to the full path is the most reliable means to ensure the correct
executables are picked up.
ie.
CC = full_path_to_ds_8_bin/cl.exe
LINK = full_path_to_ds_8_bin/link.exe
you can use the registered environment variables for
17 matches
Mail list logo
