search for: cvsopt

...be done in other spots that do similar things as well. Also, why not name the LLVM-GCC source directory something other than "dst-directory"? Maybe "llvm-gcc.src" or similar? You add a few extraneous newlines in the code. Please remove those. - my $CVSCMD = "$NICE cvs $CVSOPT -d $CVSRootDir co -P $CVSCOOPT"; + my $CVSCMD = "$NICE cvs $CVSOPT -d $CVSRootDir co -P $CVSCOOPT"; # TODO, do we still maintain the CVS tree ? 80-column violation here and in other places. Put the comment before here. (And, no, we don't maintain the CVS tree anymore.) -bw

...that do similar things as well. > Also, why not name the LLVM-GCC source directory something other than > "dst-directory"? Maybe "llvm-gcc.src" or similar? You add a few > extraneous newlines in the code. Please remove those. > > - my $CVSCMD = "$NICE cvs $CVSOPT -d $CVSRootDir co -P $CVSCOOPT"; > + my $CVSCMD = "$NICE cvs $CVSOPT -d $CVSRootDir co -P $CVSCOOPT"; > # TODO, do we still maintain the CVS tree ? > > 80-column violation here and in other places. Put the comment before > here. (And, no, we don't maintain the C...

...gs as well. >> Also, why not name the LLVM-GCC source directory something other than >> "dst-directory"? Maybe "llvm-gcc.src" or similar? You add a few >> extraneous newlines in the code. Please remove those. >> >> - my $CVSCMD = "$NICE cvs $CVSOPT -d $CVSRootDir co -P $CVSCOOPT"; >> + my $CVSCMD = "$NICE cvs $CVSOPT -d $CVSRootDir co -P $CVSCOOPT"; >> # TODO, do we still maintain the CVS tree ? >> >> 80-column violation here and in other places. Put the comment before >> here. (And, no, we don&...

...s the "standard" shell to execute the command provided as the argument to system(). In NightlyTest.pl, I have changed the program to check out both the regular llvm CVS module as well as the llvm-test module. This command is what is giving your error. The command is: (time -p ($NICE cvs $CVSOPT -d $CVSRootDir co -APR llvm; cd llvm/projects ; \ $NICE cvs $CVSOPT -d $CVSRootDir co -APR llvm-test ) ) > $CVSLog 2>&1 When your shell interprets this, it is complaining about the second open parenthesis. Bash 2.05b on Linux handles this fine. I was asking what your "default&q...

> That's weird. What is your default shell that Perl invokes with the > "system" command. This works fine with bash-2.05b. In reality :) i use this script in crontab (and run it manually with added verbose flag): ---8X-------------- #!/bin/sh - # if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ]) then mkdir

hello everybody, I have added few improvements to my patch. Please review the new patch directly. Thanks! -Rajika On Sun, Jul 6, 2008 at 9:17 PM, Rajika Kumarasiri <rajikacc at gmail.com> wrote: > hello every body. > > Here with I have attached the patch which compile the llvm-gcc using > nightly tester script. This patch add the following capabilities to the >

That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >

hello every body. Here with I have attached the patch which compile the llvm-gcc using nightly tester script. This patch add the following capabilities to the NewNightlyTester.pl script. 1. Checkout the llvm-gcc4.2 source from the SVN. 2. Compile the checkout llvm-gcc4.2 source tree. 3. Gather the configure/make out put informations. 4. Add the (3) informations to the %hash_of_data hash to be