search for: regcomp

...h the R-help archives and I found a few tips concerning the problem. I tried them (ie: I installed readline-2.2, regex-0.12, rx-1.5, and edited ./Makeconf and ./src/include/Platform.h to use the regex libraries.) and R compiled and installed with no errors. (However, configure still didn't find regcomp and I edited Makeconf and Platform.h after running configure.) Now, when I type help() R crashes and dumps the core: > help() Segmentation fault (core dumped) R also crashes when I try to run the image demo: > demo(image) demo(image) ---- ~~~~~ Type <Return> to...

...o http://llvm.org/docs/GettingStarted.html, gcc 3.4.2 should be used but I don't know if this document is up to date regarding the required software versions) Anyway I also tried with gcc version 3.4.6 (Ubuntu 3.4.6-6ubuntu5) And now, I get a bunch of errors like this one: llvm-2.9/lib/Support/regcomp.c: In function `cset* allocset(parse*)': llvm-2.9/lib/Support/regcomp.c:1050: error: invalid conversion from `void*' to `cset*' llvm-2.9/lib/Support/regcomp.c:1055: error: invalid conversion from `void*' to `uch*' llvm-2.9/lib/Support/regcomp.c: In function `void mcadd(parse*, c...

I tried on a different machine x86_64 ( vs x86 ) and I don't have these issues anymore (the tests are failing on the x86 machine because of a segmentation fault) Both builds were done using: g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) Something should be wrong with my environment... The only differences I noticed during the compilation are the following warnings (which appear several times, but

...elease build llvm[1]: Compiling Twine.cpp for Release build llvm[1]: Compiling Valgrind.cpp for Release build llvm[1]: Compiling circular_raw_ostream.cpp for Release build llvm[1]: Compiling raw_os_ostream.cpp for Release build llvm[1]: Compiling raw_ostream.cpp for Release build llvm[1]: Compiling regcomp.c for Release build UNREACHABLE executed! 0 clang 0x0000000100c268b2 llvm::SmallVectorImpl<llvm_regmatch_t>::resize(unsigned int) + 2098 1 clang 0x0000000100c26d89 llvm::SmallVectorImpl<llvm_regmatch_t>::resize(unsigned int) + 3337 2 libSystem.B.dylib 0x00007f...

...1:37, peter dalgaard wrote: > As you're dying in an else clause, a previous if () must contain the clue. Unfortunately not necessarily the matching one. > > My guess is that your TRE library is broken. The line should have matched the RE "regline" defined as > > tre_regcomp(&regline, "^[^:]+:[[:blank:]]*", REG_EXTENDED); > ...and used here: > if(tre_regexecb(&regline, line, 1, regmatch, 0) == 0) { > > but apparently does not. int tre_regcomp(regex_t *preg, const char *regex, int cflags) { return tre_regncomp(preg, rege...

On 2009-08-24 07:28, Chris Lattner wrote: > On Aug 23, 2009, at 9:01 PM, Daniel Berlin wrote: > >>> 2. Use POSIX regcomp facilities. This implies importing some >>> implementation of this interface, e.g., Windows. On Linux, BSD, etc. >>> we would try to use the platform version if available (and non- >>> buggy). >>> >> Don't do it. >> They are ridiculous slo...

An embedded and charset-unspecified text was scrubbed... Name: not available URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20091123/36ef28cf/attachment-0001.pl>

Hi, this is not a bug report since this may not be a problem with R per se. The current release of R (1.1.0) will compile cleanly on an AIX box (I have 4.3.2) but it will fail upon startup with an Illegal Instruction. I've located the problem to be in do_strsplit when R calls regcomp. This function is defined in regex.c. However, the text from regex.o doesn't find its way into the executable, R.X11, since there's also a regcomp in /usr/lib/libc.a Apparently, this confuses the system enough to completely lose its mind. When regcomp in libc.a gets called, the stack is...

...t;8.00+00") [1] "8.KK+KK" > gsub("+","K","8.00+00") Error in gsub("+", "K", "8.00+00") : invalid regular expression '+' In addition: Warning message: In gsub("+", "K", "8.00+00") : regcomp error: 'Invalid preceding regular expression' I don't understand the error message. How do I go about replacing the "+" in the string "8.00+00" with another character? Tom -- View this message in context: http://www.nabble.com/Replacing-a-%22%2B%22-in-a-strin...

...r expressions not available" and mine was "invalid regular expression". Martin Maechler has no problems with Solaris 2.5 and suggested a regular expression library was needed, e.g., regex-x.xx. Solaris 2.4 has regex.o in /usr/ccs/libgen.a and regex.h in /usr/include. configure finds regcomp and make does not show any errors compiling and loading. Hence their is no indication that R cannot find the appropriate library. As an attempted solution, I tried downloading GNU regex-0.12 and putting regex.o in src/main so that it would be available first when ld searched for links. (character.c...

On Aug 23, 2009, at 9:01 PM, Daniel Berlin wrote: >> 2. Use POSIX regcomp facilities. This implies importing some >> implementation of this interface, e.g., Windows. On Linux, BSD, etc. >> we would try to use the platform version if available (and non- >> buggy). > > Don't do it. > They are ridiculous slow, and posix made some really dumb...

...is required. This has been happening on my Darwin build environments: -- The C compiler identification is GNU 4.2.1 -- The CXX compiler identification is Clang 4.1.0 Without the manual overrides, all C sources fail to compile with: [ 4%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regcomp.c.o cd /Users/jabbey/src/llvmCommit/build/lib/Support && /usr/bin/gcc -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC -I/Users/jabbey/src/llvmCommit/build/lib/Support -I/Users/jabbey/src/llvmCommit/lib/Support -I/Users/jabbey/src/llvmCommit/build/includ...

...ldTools/include -I<2ndStageObjDir>/BuildTools/lib/Support -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3 -fomit-frame-pointer -fPIC -Wall -W -Wno-unused-parameter -Wwrite-strings -c -MMD -MP -MF "<2ndStageObjDir>/BuildTools/lib/Support/Release+Asserts/regcomp.d.tmp" -MT "<2ndStageObjDir>/BuildTools/lib/Support/Release+Asserts/regcomp.o" -MT "<2ndStageObjDir>/BuildTools/lib/Support/Release+Asserts/regcomp.d" <LLVMSRC>/lib/Support/regcomp.c -o <2ndStageObjDir>/BuildTools/lib/Support/Release+Asserts/regcomp....

...at I would appreciate some help with: 1. Config/Alloca.h is now dead. Once configure and cmake support is removed, we can zap it. Can someone remove the cmake/autoconf stuff that pokes at Config/Alloca.h? 2. Daniel's regex email. I think the right answer is to just autodetect whether regcomp/regexec etc are available (his #2). Could someone add support to autoconf/cmake to detect whether the platform already supports these? -Chris

...expression library inside LLVM. For example, we need this to extend the FileCheck test case checking tool to support regular expressions. There are three obvious options: 1. Roll our own library. Multiple unnamed individuals may even already have implementations lying around! :) 2. Use POSIX regcomp facilities. This implies importing some implementation of this interface, e.g., Windows. On Linux, BSD, etc. we would try to use the platform version if available (and non-buggy). 3. Import a more heavy weight library such as PCRE, and use it universally. My personal preference is #2, and I may...

...base, "."), "", a) :=20 invalid regular expression '/var/folders/bU/bUB3Gk1uHBuDXq1G72Xc+++++TI/-= Tmp-/RtmpGzn3kA/file60b7acd9.' Calls: <Anonymous> -> .shlib_internal -> sub In addition: Warning message: In sub(p0(base, "."), "", a) : regcomp error: 'Invalid use of repetition operators' Execution halted Browse[2]> system("R CMD SHLIB /var/folders/bU/bUB3Gk1uHBuDXq1G72Xc+++++TI/= -Tmp-/RtmpGzn3kA/file60b7acd9.cpp") Error in sub(p0(base, "."), "", a) :=20 invalid regular expression '/var/fol...

...this configuration, I'm just not sure how much I'd really want to tweak the build system to accommodate it given that there is a workaround. > > Without the manual overrides, all C sources fail to compile with: > > [ 4%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regcomp.c.o > cd /Users/jabbey/src/llvmCommit/build/lib/Support && /usr/bin/gcc -D_DEBUG > -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC > -I/Users/jabbey/src/llvmCommit/build/lib/Support > -I/Users/jabbey/src/llvmCommit/lib/Support > -I/Users/jabbey/sr...

...roduces the following error message: Error in grep("*", model) : invalid regular expression '*' In addition: Warning messages: 1: '\*' is an unrecognized escape in a character string 2: unrecognized escape removed from "\*" 3: In grep("*", model) : regcomp error: 'Invalid preceding regular expression' Execution halted Any ideas anyone? Robin -- View this message in context: http://www.nabble.com/grep-for-asterisks-%22*%22%27s-tp20644195p20644195.html Sent from the R help mailing list archive at Nabble.com.

...ng error (and a warning): > max(xxx[Error in grep(sprintf("^%s", makeRegexpSafe(text)), allArgs, value = TRUE) : invalid regular expression '^xxx[' In addition: Warning message: In grep(sprintf("^%s", makeRegexpSafe(text)), allArgs, value = TRUE) : regcomp error: 'Invalid regular expression' Now it seems that this problem in R has managed to screw up something out of R (and this is probably OS dependent, I'm running 64-bit openSUSE 10.3) because when I quit R and try to do something at the shell level, what I type is not echoed anymore...

On 2015-12-17 19:30, peter dalgaard wrote: > Presumably the file in question is one of > > Peter-Dalgaards-MacBook-Air:BUILD pd$ grep -r "^Package: tools" * > library/tools/DESCRIPTION:Package: tools > src/library/tools/DESCRIPTION:Package: tools > > so the first thing I'd do is to have a good look at those files and see if they got somehow corrupted. > >