search for: cxxflags

...RESULT([no])]); > - > - # Restore CFLAGS; VISIBILITY_CFLAGS are added to it where needed. > - CFLAGS=$save_CFLAGS > + if test "x${ax_cv_have_func_attribute_visibility}" = xyes; then > + VISIBILITY_CFLAGS="-fvisibility=hidden" > + VISIBILITY_CXXFLAGS="-fvisibility=hidden" > + fi > > # Work around aliasing bugs - developers should comment this out > CFLAGS="$CFLAGS -fno-strict-aliasing" > @@ -267,19 +264,6 @@ fi > if test "x$GXX" = xyes; then > CXXFLAGS="$CXXFLAGS -Wall&q...

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 CXXFLAGS | sed ...

...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 we want dpkg-buildflags --get CXXFLAGS? Best -k > optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS` > https://sources.debian.org/src/r-base/4.4.0-2/debian/rules/#L101 > ...which later propagares to cxxflags = $(optimflags) and > eventually CXXFLA...

...> 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` https://sources.debian.org/src/r-base/4.4.0-2/debian/rules/#L101 ...which later propagares to cxxflags = $(optimflags) and eventually CXXFLAGS="$(cxxflags)" ... ./configure. On Sid, dpkg-buildflags --get CFLAGS includes -Werror=implicit-function-declaration, which g++ doesn't like: root at 020af1fe3ba2:/# g++ -Werror=implicit-function-declaration -c ex.cpp cc1plus: warning: '-Wer...

...h_back(T &&Elt) { >> ^ >> /usr/local/include/llvm/ADT/SmallVector.h:476:33: warning: rvalue references are a C++11 extension [-Wc++11-extensions] >> iterator insert(iterator I, T &&Elt) { >> > You need to build Clang/LLVM with a {CXX, CXXFLAGS} pair (read: a c++ compiler for your host) that supports C++11. That can either be one whose default is c++11, or one that doesn't but lets you put '--std=c++11' in the CXXFLAGS. > > http://llvm.org/docs/GettingStarted.html suggests GCC >= 4.7.0 for this. Hello again, Runnin...

Hi Óscar, On 22/11/12 09:41, Óscar Fuentes wrote: > Luba Tang <lubatang at gmail.com> writes: > >> We found `llvm-config --cxxflags' does not have -fno-exceptions -fno-rtti >> when using cmake to build LLVM. >> Does anyone know how to fix it? > > Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is > no reason to impose it on client code. actually it does impact external code. For...

...ified plugin")); > > If dragonegg is compiled with RTTI then linking fails because there is no RTTI > for the cl::opt class. Thus dragonegg is forced to compile with -fno-rtti if > it wants to work with this part of LLVM. > > There is also the question of what `llvm-config --cxxflags` is supposed to mean. > Is it supposed to give the flags that LLVM was compiled with? Or is it supposed > to give the flags that users of LLVM must compile themselves with? If it's the > second why does it have optimization levels (-O2), debug info (-g) and so on, > which are not...

Hi, We found `llvm-config --cxxflags' does not have -fno-exceptions -fno-rtti when using cmake to build LLVM. Does anyone know how to fix it? Best regards, Luba ---------- Forwarded message ---------- From: Luba Tang <lubatang at gmail.com> Date: 2012/11/21 Subject: Re: [MCLinker] Re: Major release - MCLinker 2.0.0 - RockB...

On 6/16/14, 1:14 PM, Dan Liew wrote: > Hi Joseph, > >> In other words what does " put '--std=c++11' in the CXXFLAGS” mean? Do you >> have an example of what it would look like? or what should I read in order >> to learn this? I’m happy to read up but I don’t know where to start reading >> (besides the getting started page on llvm) :) > > You're still trying to build the tutorial rig...

...k I found a bug in llvm's CMakeLists.(I use llvm 3.1svn and Clang 3.1) I follow the normal way to try to compile an application that utilize both clang and llvm: I ./autogen.sh it, ./configure it and make it. But the make fails. At last I found out the failure is because that the Makefile's CXXFLAGS does not contain -fno-rtti option which is needed by the compilation. The "configure" file of the application use llvm-config --cxxflags to assign to the CXXFLAGS. But Although I see that, under my platform, almost all the the files inside LLVM and Clang are compiled with -fno-rtti, the...

Hi, I'm trying to port a piece of code using LLVM as a library to the latest SVN version. One difference between 2.6 and 2.7svn is that `llvm-config --cxxflags` now include -fno-rtti. Since my code does use RTTI information (in non-trivial dynamic_cast), my code can't compile with this. Same goes for -fexceptions. I've tried setting my CXXFLAGS to `llvm-config --cxxflags` -frtti -fexceptions, now my code compiles, but it doesn't link against...

...ot;; AC_MSG_RESULT([no])]); > - > - # Restore CFLAGS; VISIBILITY_CFLAGS are added to it where needed. > - CFLAGS=$save_CFLAGS > + if test "x${ax_cv_have_func_attribute_visibility}" = xyes; then > + VISIBILITY_CFLAGS="-fvisibility=hidden" > + VISIBILITY_CXXFLAGS="-fvisibility=hidden" > + fi > As these two are no longer GCC "specific" we can move them out of the if test x$GCC = xyes, conditional. > # Work around aliasing bugs - developers should comment this out > CFLAGS="$CFLAGS -fno-strict-aliasing&quo...

...what you didn't want: -O2. In R-exts, it says that "Flags which are set in file etc/Makeconf can be overridden by the environment variable MAKEFLAGS (at least for systems using GNU make), as in (Bourne shell syntax)" but this doesn't work if I set either MAKEFLAGS or CFLAGS/CXXFLAGS in my configure.ac script or package Makevars. Does anyone have any ideas on how to reliably override the default CFLAGS/CXXFLAGS given in Makeconf? Many thanks, Ernest

...t;> >> If dragonegg is compiled with RTTI then linking fails because there is no RTTI >> for the cl::opt class. Thus dragonegg is forced to compile with -fno-rtti if >> it wants to work with this part of LLVM. >> >> There is also the question of what `llvm-config --cxxflags` is supposed to mean. >> Is it supposed to give the flags that LLVM was compiled with? Or is it supposed >> to give the flags that users of LLVM must compile themselves with? If it's the >> second why does it have optimization levels (-O2), debug info (-g) and so on, >&gt...

Patch 1 adds a check for the compilers visibility macro to configure.ac. Patch 2 avoids redefined symbol errors in clang of the tls entry points. Based on a suggestion from Rafael Ávila de Espíndola <rafael.espindola at gmail.com> in http://llvm.org/bugs/show_bug.cgi?id=19778. Tested with gcc 4.9 and clang 3.6(rc) Marc Dietrich (2): configure: add visibility macro detection to configure

Hi r-devel, a recent install of R-3.4.0 RC (2017-04-13 r72510)? on Linux (Ubuntu 16.04.1 LTS) x86_64-linux-gnu? with?g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 (see?http://bioconductor.org/checkResults/devel/bioc-LATEST/malbec2-NodeInfo.html?for more)? results in CXXFLAGS not containing "-O2" as optimisation flag, there is only " -Wall", while?CFLAGS are happy with "-g -O2 -Wall" This has an influence in at least one place https://stat.ethz.ch/pipermail/bioc-devel/2017-April/010733.html where we have WARNINGS in R CMD check from "...

...shared library in Windows with customized level of optimization. Specifically, I would like to have "-O3 -funroll-loops" as flags when I run "R CMD SHLIB ***.cc" to speed the program for my simulations. I have read through the documentation and have tried adding the line PKG_CXXFLAGS = -O3 -funroll-loops in my Makevars in my package's src directory. However, this places the flags before the -O2 flag, thereby overriding it. I have also tried creating a config.site file in R_HOME/etc, but that seems to be ignored. I found a possible solution at http://tolstoy.newcastle.ed...

Luba Tang <lubatang at gmail.com> writes: > We found `llvm-config --cxxflags' does not have -fno-exceptions -fno-rtti > when using cmake to build LLVM. > Does anyone know how to fix it? Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is no reason to impose it on client code.

...roen 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 years ago. You cannot undo what it is in R's own /etc/R/Makeconf via a programmatic way via some sort of option or alike. It is fixed. You and I know that you can add to the right-hand side via ~/.R/Makeconf and that is about it AFAIK...

...l, > > a recent install of R-3.4.0 RC (2017-04-13 r72510)? > on Linux (Ubuntu 16.04.1 LTS) x86_64-linux-gnu? > with?g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 > (see?http://bioconductor.org/checkResults/devel/bioc-LATEST/malbec2-N > odeInfo.html?for more)? > results in CXXFLAGS not containing "-O2" as optimisation flag, > there is only " -Wall", while?CFLAGS are happy with "-g -O2 > -Wall" > > This has an influence in at least one place > https://stat.ethz.ch/pipermail/bioc-devel/2017-April/010733.html > where we have WARNI...