Re: [AMBER-Developers] AT test, weird csh,rm thing

From: Lachele Foley <>
Date: Wed, 25 Nov 2009 21:19:32 -0500

Sorry I wasn't so complete before.

[ test]$ /bin/csh --version
tcsh 6.14.00 (Astron) 2005-03-25 (x86_64-unknown-linux) options wide,nls,dl,al,kan,sm,rh,color,filec

What happens is that the "make -f Makefile_at test" does this:

[runs well for many tests, most passing and then]
diffing with ala.prep
(cd leap && ./Run.tleap)
AMBERHOME is set to /array2/programs/amber11_AT_20091124

Running leap tests on ./tleap -> ../../exe/teLeap

/bin/rm: No match.
./Run.tleap: File permission error
make: *** [test.leap] Error 1

So, the only real trouble is that this causes the entire testing to stop. If I comment out those lines in Run.tleap, the tests all proceed and things seem to work. I did notice that other tests gave /bin/rm complaints, but they didn't cause the testing to stop.

I was surprised that /bin/rm -f worked for plain csh but not for csh -f, especially because I'm using bash on this system and there isn't a .tcshrc in my home directory at all.

Some system details:

Linux 2.6.18-164.6.1.el5xen #1 SMP Tue Oct 27 11:45:55 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

Red Hat Enterprise Linux Server release 5.4 (Tikanga)

(login shell) GNU bash, version 3.2.25(1)-release (x86_64-redhat-linux-gnu)

Let me know what other info to provide.

:-) Lachele
B. Lachele Foley, PhD '92,'02
Assistant Research Scientist
Complex Carbohydrate Research Center, UGA
----- Original Message -----
From: Scott Brozell
To: AMBER Developers Mailing List
Sent: Wed, 25 Nov 2009 16:27:35
Subject: Re: [AMBER-Developers] AT test, weird csh,rm thing
> Hi,
> On Wed, Nov 25, 2009 at 12:05:01PM -0500, case wrote:
> > On Tue, Nov 24, 2009, Lachele Foley wrote:
> > > 
> > > So, invoking "csh -f" on my system causes /bin/rm to behave unexpectedly
> > > (plain csh works as expected). 
> > 
> > This is indeed odd, but some similar-sounding problems have been reported
> > before. What does "/bin/csh --version" report?
> I only found reports of requiring an csh in am-dev.
> > There are lots of test cases that begin with "#!/bin/csh -f" and later
> contain
> > a "/bin/rm -f ..." command.  Maybe it has something to do with shell
> > globbing(?).  [Most other /bin/rm commands don't use shell wild-cards.]
> > 
> > Your report is a little incomplete: what is the "trouble" that is caused
> > in the Run.tleap script?  Also, what you show about the behavior of csh
> vs.
> > csh -f looks like what I would expect -- am I missing something there?
> Yes, send verbose and verbatim details if u can reproduce the problem.
> Scott
> _______________________________________________
> AMBER-Developers mailing list
AMBER-Developers mailing list
Received on Wed Nov 25 2009 - 18:30:02 PST
Custom Search