On 2020/04/02 06:43, Andrey Repin wrote:
That's not what actually happens.
...\Documents> ls -1 *.pdf
21927-ticket.pdf
'Stars! Universe Map.pdf'
---
Thank you for your update.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentatio
Greetings, L A Walsh!
> On 2020/03/24 00:18, Jay Libove via Cygwin wrote:
>> Problem:
>> Under certain circumstances (see Steps to Reproduce, below) Cygwin programs'
>> built-in argv[] globbing will produce unexpected:
>> "{programName}: cannot access '{glob pattern}: No such file or directory"
>
On 2020/03/24 00:18, Jay Libove via Cygwin wrote:
Problem:
Under certain circumstances (see Steps to Reproduce, below) Cygwin programs'
built-in argv[] globbing will produce unexpected:
"{programName}: cannot access '{glob pattern}: No such file or directory"
e.g.
"ls: cannot access '*.pdf': No
Greetings, Jay Libove!
> I've never seen this before.
> In a Windows CMD shell, Cygwin shell expansion, for example:
> ls *.pdf
> returns:
> ls: cannot access '*.PDF': No such file or directory
> (Indeed, any Cygwin shell expansion, when executed from within Windows CMD,
> produces this error. S
Maybe it can simply be fixed by changing the order of setting up locale stuff
and applying the expansion in cygwin?
(I would look into the code if I had a clue where to find the respective
things.)
I would guess dcrt0.cc, the Cygwin DLL runtime initialization.
..mark
--
Problem reports:
uot; in Windows CMD shell, but works okay in bash " (thread starter
https://cygwin.com/pipermail/cygwin/2020-March/244161.html )
Many thanks to Paul, Andrey, and others for helping me nail down where and how
it seems to be happening.
My apologies in advance that my coding days are long behi
Am 23.03.2020 um 20:13 schrieb Andrey Repin:
Greetings, Jay Libove!
...
If I set LANG=en_US.UTF-8 in a Windows CMD window, **then the globbing problem
goes away**.
I was about to respond that cmd.exe does not do shell expansion but in
fact there is a cygwin workaround to replace it with li
Hi Cygwin team,
Here is a consolidated bug report based on the discussion in recent days which
I'd started under the subject " shell expansion produces e.g. "ls: cannot
access '*.pdf': No such file or directory" in Windows CMD shell, but works okay
in bash "
Am 23.03.2020 um 19:34 schrieb Jay Libove via Cygwin:
Hi Andrey,
(I have no idea what you mean about "top posting".)
https://lmgtfy.com/?q=top+posting+vs+bottom+posting
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:
Greetings, Jay Libove!
> Hi Andrey,
> (I have no idea what you mean about "top posting".)
https://cygwin.com/acronyms/#TOFU
> `locale` gives the same in CMD as in bash, on this machine as on another
> machine on my network where I also checked, which also exhibits the same
> globbing problem und
that points towards a solution, but it certainly must be a
clue.
thanks,
Jay
-Original Message-
From: Andrey Repin
Sent: Monday 23 March 2020 18:44
To: Jay Libove ; cygwin@cygwin.com
Subject: Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such
file or
Greetings, Jay Libove!
Please no top posting in this mailing list.
> Good suggestion, deleting files one by one. It's not just one file, but it
> does seem to have something to do with some file name patterns.
> I think I've got it. It's accented characters.
> I live in Spain. Spanish has accente
shell expansion produces e.g. "ls: cannot access '*.pdf': No
> such file or directory" in Windows CMD shell, but works okay in bash
>
> Have you tried deleting files one by one, to see if the issue is related to a
> single file (sorry if this is an obvious suggestio
in@cygwin.com
Subject: Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such
file or directory" in Windows CMD shell, but works okay in bash
Have you tried deleting files one by one, to see if the issue is related to a
single file (sorry if this is an obvious sugg
m further?
>
> thanks again,
> -Jay
>
> -Original Message-
> From: Paul Moore
> Sent: Sunday, 22 March 2020 20:09
> To: Jay Libove
> Cc: cygwin@cygwin.com
> Subject: Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No
> such f
problem further?
thanks again,
-Jay
-Original Message-
From: Paul Moore
Sent: Sunday, 22 March 2020 20:09
To: Jay Libove
Cc: cygwin@cygwin.com
Subject: Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such
file or directory" in Windows CMD shell, but works
On Sun, 22 Mar 2020 at 19:11, Marco Atzeri via Cygwin wrote:
> any reason for NOT using a cygwin shell ?
Many reasons. But that's not relevant to this thread, is it? (Note:
I'm not the OP, just an interested contributor to the thread).
I'm happy to elaborate if you want, but I suggest we do it
Am 22.03.2020 um 18:50 schrieb Jay Libove via Cygwin:
I've never seen this before.
In a Windows CMD shell, Cygwin shell expansion, for example:
ls *.pdf
returns:
ls: cannot access '*.PDF': No such file or directory
(Indeed, any Cygwin shell expansion, when executed from within Windows CMD,
prod
Is this because cygwin globbing is (by default) case sensitive? You
could set the CYGWIN environment variable to "glob:ignorecase" to get
case-insensitive behaviour.
Paul
On Sun, 22 Mar 2020 at 17:52, Jay Libove via Cygwin wrote:
>
> I've never seen this before.
> In a Windows CMD shell, Cygwin
I've never seen this before.
In a Windows CMD shell, Cygwin shell expansion, for example:
ls *.pdf
returns:
ls: cannot access '*.PDF': No such file or directory
(Indeed, any Cygwin shell expansion, when executed from within Windows CMD,
produces this error. See below)
ls *someotherwildcard* (tha
Hello. When trying to sftp a file from one Cygwin machine to another via
sftp, I get "Couldn't canonicalise: No such file or directory." on a
target directory in DOS format, unless I specify a cygdrive target
path. I do not get this error on the source directory, even though it
is also in DOS
On 5/8/2011 7:23 AM, Jens Schweikhardt wrote:
On Sun, May 08, 2011 at 01:32:12AM +0100, Olumide wrote:
...
# Now I'm running out of HD space I'm looking to reclaim some of that
# space. Is it okay to delete some or all of these directories? I'm
# concerned that the Cygwin setup p
On Sun, May 08, 2011 at 01:32:12AM +0100, Olumide wrote:
...
# Now I'm running out of HD space I'm looking to reclaim some of that
# space. Is it okay to delete some or all of these directories? I'm
# concerned that the Cygwin setup program uses one of these folders to
# determin
3a%2f%2fftp.uni-kl.de%2fpub%2fwindows%2fcygwin%2f
http%3a%2f%2fftp.gwdg.de%2fpub%2flinux%2fsources.redhat.com%2fcygwin%2f
Now I'm running out of HD space I'm looking to reclaim some of that
space. Is it okay to delete some or all of these directories? I'm
concerned that the Cygwin setup
inux.rz.ruhr-uni-bochum.de%2fcygwin
>http%3a%2f%2fftp.uni-kl.de%2fpub%2fwindows%2fcygwin%2f
>http%3a%2f%2fftp.gwdg.de%2fpub%2flinux%2fsources.redhat.com%2fcygwin%2f
>
>Now I'm running out of HD space I'm looking to reclaim some of that
>space. Is it okay to delete some or
in%2f
http%3a%2f%2fftp.gwdg.de%2fpub%2flinux%2fsources.redhat.com%2fcygwin%2f
Now I'm running out of HD space I'm looking to reclaim some of that
space. Is it okay to delete some or all of these directories? I'm
concerned that the Cygwin setup program uses one of these folder
On 7/5/2010 2:13 AM, ke...@ca wrote:
thank you all. You all are right. I got the desired dlls. Now I know I was
misleaded by the statement that GCC is a collection of compilers and it
automatically use a compiler according to a programming language.
It does this for the frontend, not the backen
not a cygwin issue, it is a "very" basic one.
>
>
>
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http
--- Dom 4/7/10, ke...@ca ha scritto:
>
> Hi there,
>
> I wrote a file, hello.c. It has only one function: print a
> message like
> "hello!".
> # hello.c #
> #include
> void hello() { printf( "Hello.\n" ) ; }
>
> $gcc -c hello.c
> $gcc -shared -o hello.dll hello.o
>
> I successuf
On 2010-07-04 10:24Z, ke...@ca wrote:
>
> $gcc -c hello.c
> $gcc -shared -o hello.dll hello.o
>
> I successufully built it as DLL, hello.dll.
Here, the C runtime library is automatically linked.
> Then, I rewrote it in c++.
[...]
> Then, I used the commands above to built DLL, but it failed. Wh
On 2010-07-04 12:27 PM, ke...@ca wrote:
Forgot to attach error information.
hello.o:hello.cpp:(.text+0xd): undefined reference to
`std::basic_string, std::allocator
::size() const'
hello.o:hello.cpp:(.text+0x60): undefined reference to
`std::basic_string, std::allocator
::operat
id hello() {cout << "Hello." << endl ;}
>
> Then, I used the commands above to built DLL, but it failed. Why did it
> fail?
>
>
--
View this message in context:
http://old.nabble.com/Building-DLLs-on-C%2B%2B-version-code-failed%2C-but-okay-on-C-version-
n, I rewrote it in c++.
# hello.cpp ###
#include
using namespace std ;
void hello() {cout << "Hello." << endl ;}
Then, I used the commands above to built DLL, but it failed. Why did it
fail?
--
View this message in context:
http://old.nabble.com/Building-DLLs-on-C%2B%2B-ve
[EMAIL PROTECTED] wrote:
> [forward some question, which I lack to understand semantically]
To answer I'd say;
Type this, as is, at the bash "$" prompt:
man bash
/^INVOCATION
Read 4th paragraph thoroughly, then go on and read more to answer any
questions that might rise from this.
And... http:/
[forward some question, which I lack to understand semantically]
--- Begin Message ---
Hello,
I had many troubles with installing cygwin on my laptop, and finally
(after one week...) the only way to make it work was to download and
install directly from Internet!
I have one little question, but i
On Fri, 25 Oct 2003, Uwe Dippel wrote:
> Tried archives, google, erdelynet; but no answer or unrelated.
> Newbie on XP.
> Install okay, can log on locally (XP) as admin and users. Remote logon
> (Linux - ssh) works for admin of XP box only; not for any of the users
> on that XP bo
Tried archives, google, erdelynet; but no answer or unrelated.
Newbie on XP.
Install okay, can log on locally (XP) as admin and users. Remote logon
(Linux - ssh) works for admin of XP box only; not for any of the users
on that XP box. I tried some of those posts suggesting mkpasswd and
mkgroup; no
18 July, 2003 23:17
> To: guenter strubinsky; [EMAIL PROTECTED]
> Subject: Re: okay!
>
> Which is?
>
> - Original Message -
> From: "guenter strubinsky" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday,
Which is?
- Original Message -
From: "guenter strubinsky" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 18, 2003 5:21 PM
Subject: okay!
> This solution just screamed at me!
>
>
>
> --
> Unsubscribe info: http://cyg
This solution just screamed at me!
--
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/
At 11:07 AM 5/3/2002, Rick Hellicar (QMP) wrote:
>Larry Hall wrote:
> > At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote:
> >> Hi all,
> >>
> >> I'm modifying some old code I last compiled in October 2000. The code uses a
>3rd-party DLL, which
> >> comes with an import library. It used to link wit
Larry Hall wrote:
> At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote:
>> Hi all,
>>
>> I'm modifying some old code I last compiled in October 2000. The code uses a
>3rd-party DLL, which
>> comes with an import library. It used to link without fuss against that import
>library and run perfectly.
>
At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote:
>Hi all,
>
>I'm modifying some old code I last compiled in October 2000. The code uses a
>3rd-party DLL, which
>comes with an import library. It used to link without fuss against that import
>library and run perfectly.
>
>I've moved on to cygwin_1
Hi all,
I'm modifying some old code I last compiled in October 2000. The code uses a 3rd-party
DLL, which
comes with an import library. It used to link without fuss against that import library
and run perfectly.
I've moved on to cygwin_1.3.10, gcc version 2.95.3-5, and I now get a host of
"un
Thanks Gerrit, it worked much better!
Gerrit P. Haase wrote:
> Hallo Peter,
>
> Am 2001-12-11 um 22:35 schriebst du:
>
>
>>I compiled perl and when I do "make test" I only get 96% okay-
>>Searching the MLA I see that some people have gotten 99+% okay- is
Hallo Peter,
Am 2001-12-11 um 22:35 schriebst du:
> I compiled perl and when I do "make test" I only get 96% okay-
> Searching the MLA I see that some people have gotten 99+% okay- is there
> something special I need to do to build perl under cygwin? I just did a
> conf
Peter Buckley wrote:
>
> I compiled perl and when I do "make test" I only get 96% okay-
> Searching the MLA I see that some people have gotten 99+% okay- is there
> something special I need to do to build perl under cygwin? I just did a
> configure -d to accept all the
I compiled perl and when I do "make test" I only get 96% okay-
Searching the MLA I see that some people have gotten 99+% okay- is there
something special I need to do to build perl under cygwin? I just did a
configure -d to accept all the defaults.
TIA,
Peter
--
Your mouse has move
48 matches
Mail list logo
