search for: argstr

...OSSIM_SDK_DIR}) >> >> where IOSSIM_SDK_DIR is the path including spaces and parens. > > It looks like the _CFLAGS values are used in the module > cmake/Modules/CompilerRTUtils.cmake: > > function(set_target_compile_flags target) > foreach(arg ${ARGN}) > set(argstring "${argstring} ${arg}") > endforeach() > set_property(TARGET ${target} PROPERTY COMPILE_FLAGS "${argstring}") > endfunction() > > but that makes no attempt to escape or quote anything. > > The COMPILE_FLAGS target property was a very early CMake feat...

Dear R-help, Can some one tell me how to do the following (if it's possible)? Suppose I have a function like this: f <- function(x, y, ...) { ## some code g(x, y, ...) ## some more code } The problem is that g() may not understand everything that comes through in "...". Is there a way to delete some component of "..." and then pass it to g()? Here's

...ming word expansion. For example, expari will skip backwards looking for the start of the arithmetic expansion, while evalvar will skip unexpanded words manually. This is cumbersome and error-prone. This patch fixes this by making word expansions proceed in a linear fashion. This means changing argstr and the various expansion functions such as expari and subevalvar to return the next character to be expanded. This is inspired by similar code from FreeBSD. However, we take things one step further and completely remove the manual word skipping in evalvar. This is accomplished by introducing a...

...it;h=4bfffb1572c9d1b77538b5a3e92c27f91bd2ee99 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 25 Feb 2019 14:00:31 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: expand: Fix double-decrement in argstr [ dash commit 86a841bb444ed1d9a09afb38cb818a21c04e1beb ] Due to a double decrement in argstr we may miss field separators at the end of a word in certain situations. Reported-by: Martijn Dekker <martijn at inlv.org> Fixes: 3cd538634f71 ("expand: Do not reprocess data when...") Si...

...#39;t be executed. I found the following, but didn't trace through to verify exactly where I was in the code base: --- options.c --- 1785 /* We make use of the -e option to let the server know about any 1786 * pre-release protocol version && some behavior flags. */ 1787 argstr[x++] = 'e'; 1788 #if SUBPROTOCOL_VERSION != 0 1789 if (protocol_version == PROTOCOL_VERSION) { 1790 x += snprintf(argstr+x, sizeof argstr - x, 1791 "%d.%d", PROTOCOL_VERSION, SUBPROTOCOL_VERSION); 1792 } else 1793 #endif 1794 argstr[x++] =...

...==================================================== --- options.c +++ options.c 2008-03-19 18:38:56.000000000 +0100 @@ -1837,14 +1837,14 @@ /* We make use of the -e option to let the server know about any * pre-release protocol version && some behavior flags. */ - argstr[x++] = 'e'; #if SUBPROTOCOL_VERSION != 0 + argstr[x++] = 'e'; if (protocol_version == PROTOCOL_VERSION) { x += snprintf(argstr+x, sizeof argstr - x, "%d.%d", PROTOCOL_VERSION, SUBPROTOCOL_VERSION); } else...

...i in 1:d) { if(is.null(indlist[[i]])) { indvecstr[i] <- ""; } else{ indvecstr[i] <- paste("c(",paste(indlist[[i]],sep="",collapse=","),")",sep="") } } #Then build up the argument string to "[" argstr <- paste(indvecstr,sep="",collapse=",") argstr <- paste("x[",argstr,"]",sep="") #Finally, return the subsetted array return(eval(parse(text=argstr))) } -- Dr. Balaji S. Srinivasan Stanford University Depts. of Statistics and Com...

A couple of llvm sub-projects have been failing to build for me for a while (compiler-rt asan and util/unittests, at least). It turns out to be due to the fact that some paths on my system include spaces and other special characters, but the the build.ninja file was not generated with correctly quoted strings. Specifically I'm on OS X and the command is setting -isysroot to a location inside

...arget, which looks fine to me: -- {CAN_TARGET_x86_64}: TRUE -- {CMAKE_BINARY_DIR}: /home/mohit/compiler-rt_build -- {SIMPLE_SOURCE}: /home/mohit/compiler-rt_build/CMakeFiles/simple.cc -- {TARGET_x86_64_CFLAGS}: -m64 -- TARGET_{arch}_OUTPUT: TARGET_x86_64_OUTPUT -- -DCMAKE_EXE_LINKER_FLAGS:STRING={argstring}:-DCMAKE_EXE_LINKER_FLAGS:STRING= -m64 -- {CAN_TARGET_i386}: FALSE -- {CMAKE_BINARY_DIR}: /home/mohit/compiler-rt_build -- {SIMPLE_SOURCE}: /home/mohit/compiler-rt_build/CMakeFiles/simple.cc -- {TARGET_i386_CFLAGS}: -m32 -- TARGET_{arch}_OUTPUT: TARGET_i386_OUTPUT -- -DCMAKE_EXE_LINKER_FLAGS:...

In debian bug #493559 (http://bugs.debian.org/493559) the problem is that when requesting a file from an older version rsync, the remote server gives an error: $ rsync rsync://rsync.blackholes.us/zones/countries/countries.rbl /tmp rsync: on remote machine: -: unknown option rsync error: requested action not supported (code 4) at clientserver.c(517) rsync: connection unexpectedly closed (4 bytes

...), here's a patch to enable safe incremental file lists between a 3.1.0 client and a pre 3.1.0 daemon (protocol version 30) --- options.c.ORIG 2013-06-12 06:28:45.000000000 +1000 +++ options.c 2013-10-21 12:46:25.251082555 +1100 @@ -2477,6 +2477,8 @@ #ifdef ICONV_OPTION argstr[x++] = 's'; #endif + if (protocol_version == 30) + argstr[x++] = 'f'; } if (x >= (int)sizeof argstr) { /* Not possible... */ thanks, /Per Lundqvist

...quot;, 'S', POPT_ARG_NONE, &sparse_files, 0, 0, 0 }, {"cvs-exclude", 'C', POPT_ARG_NONE, &cvs_exclude, 0, 0, 0 }, @@ -798,6 +801,8 @@ void server_options(char **args,int *arg /* the -q option is intentionally left out */ if (make_backups) argstr[x++] = 'b'; + if (do_fsync) + argstr[x++] = 'f'; if (update_only) argstr[x++] = 'u'; if (dry_run) --- rsync-2.6.1/util.c.bak 2004-04-23 01:17:15.000000000 +0300 +++ rsync-2.6.1/util.c 2004-04-27 19:15:29.000000000 +0300 @@ -29,6 +29,7 @@ extern int verbose; exter...

We use rsync to update an nfs server. After an update, we noticed that a large number of clients didn't see the updated data. It took me a while to be able to reliably reproduce this problem, but it happens on old and new versions of rysnc. It also happens across all the platforms we use here (sun/linux/netapp). This shows the problem: [Note my home directory is NFS mounted]

People of cygwin & rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a "get" (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

Synopsis: Prior to the 2.6.4pre versions, issuing 'rsync rsync://host/module/' behaved effectively as 'ls -l'. I've toyed with various options in an attempt to get an 'ls -l' style output, but to no avail. As I have a small handful of scripts that rely on this no-longer-functioning functionality, this could be considered a Bad Thing(TM). Following is an example of

.../* Checking the pre-negotiated value allows --protocol=29 override. */ if (protocol_version >= 30) { /* We make use of the -e option to let the server know about * any pre-release protocol version && some behavior flags. */ argstr[x++] = 'e'; The server is using version 26 and probably doesn't support -e.s anyway. Why is rsync ignoring the negotiated protocol version and sending unsupported options ? -- Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 (Pacific Time)

...int quoted; varflags = *p++; @@ -713,41 +714,41 @@ again: if (varflags & VSNUL) varlen--; + discard = varlen < 0 ? EXP_DISCARD : 0; + switch (subtype) { case VSPLUS: - varlen = -1 - varlen; + discard ^= EXP_DISCARD; /* fall through */ case 0: case VSMINUS: - p = argstr(p, flag | EXP_TILDE | EXP_WORD); - if (varlen < 0) - return p; + p = argstr(p, flag | EXP_TILDE | EXP_WORD | + (discard ^ EXP_DISCARD)); goto record; case VSASSIGN: case VSQUESTION: - if (varlen >= 0) - goto record; - p = subevalvar(p, var, 0, startloc, varflags, -...

...the daemon to recurse the target directory tree anyways. Here's the code: in options.c: /* this is a complete hack - blame Rusty this is a hack to make the list_only (remote file list) more useful */ if (list_only && !recurse) argstr[x++] = 'r'; in exclude.c: /* This is a complete hack - blame Rusty. * * FIXME: This pattern shows up in the output of * report_exclude_result(), which is not ideal. */ if (list_only && !recurse) { add_exclude("/*/*&q...

...ile loading shared libraries: libclangFrontend.so.7: cannot open shared object file: No such file or directory [root at localhost ~]# /usr/share/bcc/tools/opensnoop Traceback (most recent call last): File "/usr/share/bcc/tools/opensnoop", line 19, in <module> from bcc import ArgString, BPF File "/usr/lib/python3.6/site-packages/bcc/__init__.py", line 27, in <module> from .libbcc import lib, bcc_symbol, bcc_symbol_option, _SYM_CB_TYPE File "/usr/lib/python3.6/site-packages/bcc/libbcc.py", line 17, in <module> lib = ct.CDLL("libb...