I am experiencing the same delay with findutils 4.2.10-5. If I downgrade
to an older version of findutils, the delay goes away. On my system,
`find' was taking 30-40 seconds to start. I found that after I removed a
bad mapped network drive, the delay dropped to 6-7 seconds for `find' to
start.
Can anyone tell me what the purpose of the coreutils `link' program is?
It seems to just be a less functional version of `ln', so I don't know
why anyone would bother including it. It definately breaks my builds by
supplanting MSVC's `link' program in my path. I'd like to just remove
it from
The recent change of installing coreutils with `link.exe' has introduced
a *new* problem with configurations using Microsoft Visual C++ with
Cygwin's GNU `make'. Previously, one could specify "LD=link" in a
Makefile, but now the corutils `link' will supplant Microsoft's linker,
breaking builds
Well, rather than hacking my build system, I've opted to build my own
installer for Cygwin the does not contain programs that are causing me
grief. I know that some people don't want to hear that we use MS VC++
with Cygwin, but hey, this is the real world here. Cygwin helps our
productivity,
ylor wrote:
On Tue, Dec 28, 2004 at 11:15:09PM -0700, Isaac Foraker wrote:
Well, rather than hacking my build system, I've opted to build my own
installer for Cygwin the does not contain programs that are causing me
grief. I know that some people don't want to hear that we use MS VC
ust plain sucks.
Thanks for making such a useful tool available to the public.
IF
Christopher Faylor wrote:
On Tue, Jan 04, 2005 at 09:50:02AM -0700, Isaac Foraker wrote:
That's a really nice attitude. I don't expect anyone to bend over
backwards, but a little QC would be nice.
perl foo.pl
gmake: execvp: perl: Permission denied
gmake: *** [default] Error 127
#perl foo.pl
Success.
You may also need to "rm /usr/bin/perl.exe" before you can "ln -s /usr/bin/perl5.8.5.exe
/usr/bin/perl".
IF
Tue, 7 Sep 2004 18:34:30 -0400, Christopher Faylor wrote:
On Tue, S
.
Renaming gmake back to make gives the same result.
#which make
/usr/bin/make
#make
perl foo.pl
make: execvp: perl: Permission denied
make: *** [default] Error 127
Thanks,
IF
Igor Pechtchanski wrote:
On Tue, 7 Sep 2004, Isaac Foraker wrote:
Yes, the perl soft link works from the command line
6/4/2) 2004-09-07 15:07 i686 unknown unknown Cygwin
$
There must be something peculiar to your installation. Does the exact
recipe above work for you?
Igor
On Tue, 7 Sep 2004, Isaac Foraker wrote:
As stated in my original post, I renamed make.exe to gmake.exe to avoid
a name conflict w
->
/usr/bin/perl5.8.5.exe
# perl -v
This is perl, v5.8.5 built for cygwin-thread-multi-64int
...
# uname -a
CYGWIN_NT-5.1 xcoisaacf20 1.5.11(0.116/4/2) 2004-09-04 23:17 i686
unknown unknown Cygwin
Thanks,
IF
Christopher Faylor wrote:
On Tue, Sep 07, 2004 at 05:15:27PM -0600, Isaac Foraker wr
Running chmod a+x /usr/bin/perl* does not help.
Thanks,
IF
Christopher Faylor wrote:
On Tue, Sep 07, 2004 at 10:35:43PM -0600, Isaac Foraker wrote:
# ls -lL /usr/bin/perl.exe
ls: /usr/bin/perl.exe: No such file or directory
Some other possibly useful stuff:
# ls -lL /usr/bin/perl
-rwxr-x
of commands
below worked for you or not.
Ah, another possibly relevant point: I use perl 5.8.2-1... Could you
please try that?
Igor
On Tue, 7 Sep 2004, Isaac Foraker wrote:
#uname -a
CYGWIN_NT-5.1 xcoisaacf20 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown
Cygwin
I tried this sam
I just tried this, and things get worse. With 5.8.2-1, perl.exe won't
run from make. I've reinstalled Cygwin from scratch to try to clean out
anything that could be causing problems, but no luck. These are all the
commands I ran to reproduce the problem with 5.8.2.
#uname -r
1.5.11(0.116/4/2
Funny you should say that. My boss and I just discovered that as the
culprit. There is a bug that only manifests in 1.5.11. Even though
'which perl' shows /usr/bin/perl, make was running /usr/local/bin/perl.
The version of /usr/local/bin/perl somehow lost it's 'x' attribute, so
it couldn't
I just tried this and had the same problem:
> echo "Hello" > Stuff
> rm -f Stuff
> echo "Goodbye" > Stuff
Stuff: Permission denied.
> ls -l Stuff
ls: Stuff: No such file or directory
> tcsh --version
tcsh 6.13.00 (Astron) 2004-05-19 (i386-intel-posix) options
8b,nls,dl,al,kan,rh,color,dspm
> uname
You need to "net use" the network drive before you can access it through
cron.
IF
Andrea M wrote:
I am having a problem running a simple bash script with cron. The
script executes and behaves as expected when run from the command
line, but when run by cron, it fails to execute some commands.
I
16 matches
Mail list logo
