similar to: Default CXXFLAGS

On 21 May 2024 at 13:01, Jeroen Ooms wrote: | Compiling packages with C++ code using the default r-base-dev | configuration on debian:sid shows a lot of: | | cc1plus: warning: '-Werror=' argument | '-Werror=implicit-function-declaration' is not valid for C++ | | Can this flag be removed from R CMD config CXXFLAGS? "No." That was quoting Simon Urbanek from a few

On Tue, 21 May 2024 07:08:02 -0500 Dirk Eddelbuettel <edd at debian.org> wrote: > You cannot undo what it is in R's own /etc/R/Makeconf via a > programmatic way via some sort of option or alike. I think this is about the following line in debian/rules: optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS`

>>>>> Ivan Krylov writes: > On Tue, 21 May 2024 07:08:02 -0500 > Dirk Eddelbuettel <edd at debian.org> wrote: >> You cannot undo what it is in R's own /etc/R/Makeconf via a >> programmatic way via some sort of option or alike. > I think this is about the following line in debian/rules: Without having looked in much detail, I guess foer the CXXFLAGS

On Tue, 21 May 2024 14:48:48 +0200 Kurt Hornik <Kurt.Hornik at wu.ac.at> wrote: > I guess foer the CXXFLAGS we want dpkg-buildflags --get CXXFLAGS? It must be the case. It's both the documented option [1] and it currently differs from CFLAGS in the offending flag: root at 93e09ba5b6fb:/# diff -u <(dpkg-buildflags --get CFLAGS | sed 's/ /\n/g') <(dpkg-buildflags --get

Why is it that R places CFLAGS after PKG_CFLAGS and not before when compiling a package (e.g. through R CMD build pkg)? This can be problematic if, for instance, you want to use -O3, but -O2 is in R_HOME/etc/Makeconf. If -O2 (in CFLAGS) appears after -O3 (in PKG_CFLAGS), you are left with what you didn't want: -O2. In R-exts, it says that "Flags which are set in file etc/Makeconf

Does anybody know why two "-g" flags appear in the call to gcc in R CMD SHLIB Example: gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -fpic *-g* -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 *-g* -c c_file1.c -o c_object1.o Surely it need only be listed once? Alan [[alternative HTML version deleted]]

As far as I can see, and even test, R COMPILE CXXFLAGS="..." foo.c works just fine and passes the desired options on to gcc/g++. I have not been able to find a way to do this with R INSTALL foo*.tar.gz, other than by edting $RHOME/etc/Makeconf. While editing Makeconf is probably good enough for most users, it is not something I can do during (automated, unattended) builds of Debian

On 12 November 2016 at 07:59, Dirk Eddelbuettel wrote: | | On 12 November 2016 at 14:23, Kirill M?ller wrote: | | Thanks. I have now CXX = g++ -std=c++98 in my /etc/R/Makeconf, it's | | picked up properly. I can only assume that the last -std= option wins if | | more than one are given on the same command line [1]. | | Good to know it works. | | I am still a little puzzled why it was

I'm trying to run some of the test suite using the instructions here: http://llvm.org/docs/TestingGuide.html#quicktestsuite I've built llvm myself, but I'm using pre-built binaries of llvm-gcc (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). Here's what happens: foad at debian:~/svn/llvm-project/test-suite/trunk$ ./configure

I'm getting this build error with -Werror: [off-opt] : [llvm] cc1plus: warnings being treated as errors [off-opt] : [llvm] /ptmp/dag/llvm/official/llvm/lib/Target/ARM/ARMISelLowering.cpp: In member function 'llvm::MachineBasicBlock* llvm::ARMTargetLowering::EmitAtomicBinary64(llvm::MachineInstr*, llvm::MachineBasicBlock*, unsigned int, unsigned int, bool, bool) const': [off-opt]

On Thu, Dec 04, 2014 at 08:28:32PM -0500, Manu Gupta wrote: > I was trying to build Han's code and was stuck here. It seems to me that > his code is trying to generate pdf for them. > > Is it possible to modify the make files to stop building the documentation. You can run the top-level configure with --disable-documentation. Cheers, Olly

Hi, What is the difference between the R installation from source and the R installation from ubuntu repositories. Specifically when I install R-3.1.1 on ubuntu 14.04 from sources ldflags and CXXFLAGS are different that those from the installation from a repo. Installation from sources: R CMD config --ldflags -Wl,--export-dynamic -fopenmp -L/home/prana/prana_R/third-party/install/lib/R/lib

Hello, I'm writing an R package that is mainly written in C++. By default, R CMD INSTALL creates C/C++ flags as follows: -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g However, my package is fairly large. With debug info compiled into the library, the generated .so file is over 200MB. Without debug info, it's about 30MB. I hope

On Mon, Oct 9, 2017 at 4:42 PM, Tom Callaway <tcallawa at redhat.com> wrote: > > On 10/09/2017 11:16 AM, Paul Smith wrote: >> >> I am trying to install >> >> igraph package >> >> but getting the following error: >> >> ------------------ >> make: *** [/usr/lib64/R/etc/Makeconf:159: foreign-graphml.o] Error 1 >> ERROR:

On Mon, Jun 16, 2014 at 4:10 AM, lvqcl <lvqcl.mail at gmail.com> wrote: > Erik de Castro Lopo wrote: > >> Ok, done for the autotool build system. Would appreciate it if someone >> could look that the VS build files. > > > I'll do it, but: I cannot build 32-bit flac with MinGW: > > <-------------------------------------------------------------> >

After upgrading to Ubuntu 16.10, which brings GCC 6, I've noticed that packages are compiled in C++14 mode by default. Here's what a g++ command for compiling one of Rcpp's modules look like on my system: g++ -I/usr/share/R/include -DNDEBUG -I../inst/include/ -fpic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -c

Dear All, I am trying to install igraph package but getting the following error: ------------------ make: *** [/usr/lib64/R/etc/Makeconf:159: foreign-graphml.o] Error 1 ERROR: compilation failed for package ?igraph? * removing ?/usr/lib64/R/library/igraph? ------------------ Any ideas? Thanks in advance, Paul

Hi, > I'm trying to run some of the test suite using the instructions here: > > http://llvm.org/docs/TestingGuide.html#quicktestsuite > > I've built llvm myself, but I'm using pre-built binaries of llvm-gcc > (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). > > Here's what happens: the llvm testsuite (from svn, right?) uses

Hello~! I’m beginner about LLVM. My purpose is inserting a function call to basic block, which is composed of IR codes. For this, I did following works. 1) Generate bytecodes from c++ codes 2) Generate the C++ codes, composed of LLVM APIs. $ llc -march=cpp main.bc -o=main_irgen.cpp 3) Insert function call APIs to the generated C++ codes from step 2) 4) Compile the functional call

On Wed, Aug 29, 2018 at 10:14 AM, Hans Wennborg <hans at chromium.org> wrote: > On Wed, Aug 29, 2018 at 9:45 AM, Sedat Dilek via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC >> mainatiners want two things... >> >> [ FULL CMAKE LINE ] >> >> How do I