Displaying 3 results from an estimated 3 matches for "propagares".
Did you mean:
propagages
2024 May 21
1
Default CXXFLAGS
...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`
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: warnin...
2024 May 21
1
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
2024 May 21
1
Default CXXFLAGS
...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 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...