similar to: [LLVMdev] llvm-config suggestion

Well, we had llvm-config in tools originally and moved it out because it isn't really a tool. Furthermore, it doesn't work 100% yet and probably won't until after 1.7. I can move it if that's where you want it. Reid. On Wed, 2006-04-12 at 23:25 -0500, Chris Lattner wrote: > I recently tried out llvm-config: > > % llvm-config --help > tcsh:

> Bash 2.05b on Linux handles this fine. I was asking what > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > Perhaps you can: > > SHELL=/usr/bin/bash ; export SHELL > > in your script below just before it runs NightlyTest.pl? I'm not sure if > that will work or not. I have: SHELL=/bin/tcsh sh, csh, tcsh not support nested () OK, root

[in an attempt to provide system.test <- function(...) { system(paste("test", ...)) == 0 } and then file.exists <- function(file){sapply(file, function(f)system.test("-e", f))} (which would provide S-plus [>= 4.x] compatibility) ] Look at this -- ``the horror'' to me : > (system("test -e /tmp")) sh: test: argument expected [1]

On Fri, December 15, 2017 2:34 pm, Stephen John Smoogen wrote: > On 15 December 2017 at 13:24, Valeri Galtsev <galtsev at kicp.uchicago.edu> > wrote: >> Dear Experts, >> >> After one of updates that was released some time ago (a Month ago or >> maybe >> even earlier) I have noticed the following. On the machines with default >> runlevel 5 (sorry

I'm using R 1.6.1 on Windows 95 with cygwin bash as my shell. The 'shell' command tries to determine which shell the user prefers via the following steps: shell <- Sys.getenv("R_SHELL") if (!nchar(shell)) shell <- Sys.getenv("SHELL") if (!nchar(shell)) shell <- Sys.getenv("COMSPEC") For me, shell

Well, there's a bug in the globbing for the tcsh with 5.4, and my boss has filed a bug report. Meanwhile, I downgraded tcsh on those systems whose users use that as their shell. Until it's resolved, he wants me to pin the version. Googling, I see someone a few years ago, answering someone's question, suggested adding exclude=openoffice* near the top of /etc/yum.conf. I also see, more

Okay, I'll have to fix NightlyTest.pl not to use shell script syntax that isn't universal. Look for a commit soon. Reid. On Sun, 2004-09-05 at 13:31, Vladimir Merzliakov wrote: > > Bash 2.05b on Linux handles this fine. I was asking what > > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > > Perhaps you can: > > > >

I've modified the "$RHOME/bin/R" and "$RHOME/cmd/filename" so that you can use the same directories for multiple machines. That is, machines running various flavors of UNIX can access the same directories. The modified structure adds the directories $RHOME/bin/$OSTYPE/ $RHOME/lib/$OSTYPE/ to hold the machine specific binaries. For instance, here the $RHOME directory

I've modified the "$RHOME/bin/R" and "$RHOME/cmd/filename" so that you can use the same directories for multiple machines. That is, machines running various flavors of UNIX can access the same directories. The modified structure adds the directories $RHOME/bin/$OSTYPE/ $RHOME/lib/$OSTYPE/ to hold the machine specific binaries. For instance, here the $RHOME directory

All, The current SVN repository has several modules at the top level (llvm, test-suite, java, stacker, etc.). The modules contain the software that makes up the LLVM Project. However, there is nothing at the top level that explains any of this. So, I am considering doing the following at the top level of the repository (i.e. in http://llvm.org/svn/llvm-project): 1. /README.html Just a short

On Fri, April 24, 2015 12:04 pm, John R Pierce wrote: > On 4/24/2015 9:47 AM, Gordon Messmer wrote: >> On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: >>> if you leave it out the script will run in whatever environment it >>> currently is in. >> >> I'm reasonably certain that a script with no shebang will run with >> /bin/sh. I interpret your

I'm trying to learn about the tcltk package and its uses. Floundering around a bit ... Have discovered Peter Dalgaard's articles in R-News, which should help. Also James Wettenhall's suite of examples look like they might be enlightening, even though the indications are that they are Windoze oriented. Be that as it were, I decided to fool around a bit with Tcl/Tk *outside* of R to

Actually, I'm talking about the shell that Perl invokes. When you run the NightlyTest.pl script, it uses Perl. The system() function in Perl invokes 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

Dear Experts, After one of updates that was released some time ago (a Month ago or maybe even earlier) I have noticed the following. On the machines with default runlevel 5 (sorry about old terminology, the new one is still confusing for me ;-) GUI/X11 login (display manager) lists only users whose default shell is bash. Or, at least users whose default shell is tcsh are not listed at all, and if

Hi, I noticed two things when running jexec. I run FreeBSD 9.2-RC1 from binaries and jails 9.2-RC1 too. I log as root on the host (I havn't any other user). # 1. $HOME For a jail named "blog" with a "blog" user, which $HOME is at /home/blog, if I do: jexec -U blog blog tcsh My id is correct, but $HOME is still root. # 2. Accessing a jail in ssh command line I'm

> > On 24/06/15 02:55, David Minard wrote: >> On 23/06/15 13:32, David Minard wrote: >> >>> I've Set up a DC and a Member Server for a file server. Both are >>> running on Centos7 and samba version 4.2.2. The Member Server is >>> running smbd and winbindd. >>> >>> I've followed the wiki and for the most part

On Wed, Nov 5, 2014 at 10:01 AM, Philip Reames <listmail at philipreames.com> wrote: > Would one of you mind taking a step back and explaining what you believe > the "stack colouring problem" to be? I'm familiar with the general meaning > of the term and even some of LLVM's implementation; I'm just not sure what > specific issue you're referring to.

I'm noticing that logrotate's default configuration for rotating /var/ log/secure and /var/log/messages partially fails if root's shell is set to /bin/tcsh (via chsh). (Running on CentOS 4.4; logrotate-3.7.1-5.RHEL4). What seems to be happening is that the logrotate.d/syslog postrotate command runs: /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null

On 23/06/15 13:32, David Minard wrote: > I've Set up a DC and a Member Server for a file server. Both are running on Centos7 and samba version 4.2.2. The Member Server is running smbd and winbindd. > > I've followed the wiki and for the most part it's working. However, after stuffing up the ranges, then fixing them up, when I create new accounts, adding all the

On 25/06/15 13:44, David Minard wrote: >> On 24/06/15 02:55, David Minard wrote: >>> On 23/06/15 13:32, David Minard wrote: >>> >>>> I've Set up a DC and a Member Server for a file server. Both are >>>> running on Centos7 and samba version 4.2.2. The Member Server is >>>> running smbd and winbindd.