First off, I know this is slightly offtopic since it mentions a program
(ntemacs) which is not part of cygwin, but I figured I would just chime in
with a finding which may be potentially useful to cygwin users who use
ntemacs.
I use ntemacs in preference to the cygwin /usr/bin/emacs, because of th
I find that I can successfully pass long args to echo.exe using the @arglist
method. It is not too convenient though as using cmd.exe for a shell is
pretty awful. And I couldn't get g++ to work under cmd.exe ("The dynamicl
link library cygwin1.dll could not be found...")
For the time being, I gues
> Igor wrote:
> You may be hitting the command-line limit with bash. Try the above with
> cmd.exe. See below.
>> c:\cygwin\bin\echo.exe %PATH%-- works fine
>> c:\cygwin\bin\echo.exe %PATH%%PATH% -- fails, immediately returns to
command line
>
>Try stracing the last line above...
>
Igor wrote:
>Matt,
>
>A virus checker *shouldn't* affect your command line length limit...
>Try running the offending command under strace, e.g.,
>
>strace -o echo.strace /usr/bin/echo ${PATH}${PATH}
>
>and look at the tail of the output. That should give you a clue of where
>it's hanging. If y
I've had the same problem for a couple of months (since 1.3.13 anyway);
certain long command lines just fail to work for me. I've updated to the
most recent (1.30.20-1 as of march 11) and I find the problem just got worse
for me.
If I cd to a directory with many files, I issue "ls *" and the termi
A while ago I posted a weird bug; it's something I can work around but I
figured that I should write up a better description. I don't see this bug on
every machine I use, which makes it especially puzzling.
On NT4, I see the following: I find that once a command line exceeds a
certain number of c
Just another followup (currently on 1.3.15-2)
I found the hexadecimal example didn't work from scratch any more, so I
tried this:
$ for k in a b c d e f g h i j k l m n o p q r s t u v w x y z; do for j in
a b c d e f g h i j k l m n o p q r s t u v w x y z; do echo $j.$k; touch
$j.$k; done; don
Still having problems with long arg lists on nt4.
I did have two copies of cygwin1.dll, but they were identical. I deleted the
one in c:\winnt\system32 (which I put there because some programs complained
about not being able to find cygwin1.dll). I rebooted; this didn't fix
anything.
I completel
I reported a strange hang with nt4 yesterday and have more information on
how to replicate. Basically, long command line globs seem to cause the
system to get locked up at 100%. The following can replicate
mkdir tmp; cd tmp
for k in 0 1 2 3 4 5 6 7 8 9 a b c d e f
do
for j in 0 1 2 3 4 5 6 7 8
Not sure if this is a bug or not, so here goes:
I was trying to figure out why I was having trouble with nt4 seeming to hang
when I pass a long list of args to a command. The following command works
just fine.
echo *.o > foo.txt
The above produces a file that is 1918 characters long; no
Thanks,
I have everything working now, and have made loads of notes. I had to do
everything with -mno-cygwin and this made linking against c++ libs a bit
tricky (Solution: google for mingw-extras and install them). The reason I
used -mno-cygwin is that I found excel was core dumping when I linked
I've searched on google for some references to interfacing cygwin with win32
dll's. I've made a little progress but am kind of stuck creating DLL's
inside cygwin. The method I am using is the following:
/* foo.c */
#include
int WINAPI foobar() { return 1234; }
gcc -mno-cygwin foo.c -c
gcc -Wl,-
Hi,
I am having some difficulty with g++ after upgrading cygwin. Here's a sample
$ g++ -v foo.cpp
[output snipped, in an attempt to get thru spam filter]
Command returns error 1. It always returns error 1.
A partial solution:
I can just use gcc-2. However, the executables it generates must
13 matches
Mail list logo
