On Tue, Oct 10, 2017 at 04:26:26PM +0200, Joerg Sonnenberger wrote:
> On Tue, Oct 10, 2017 at 02:59:14PM +0200, Petar Bogdanovic wrote:
> > Is this the right way to solve this? I expected some setting that is
> > not compiler-specific, something like USE_LANGUAGES+=c++11 that clang,
> > for example, then also could use.
>
> No. It must be a global setting to work properly. I.e. in mk.conf before
> any C++ packages are installed (including libtool).
USE_LANGUAGES or GCC_REQD? Because setting USE_LANGUAGES+=c++11
globally seems a bit weird.
Also, compiler.mk says:
# USE_LANGUAGES
#
# Declares the languages used in the source code of the package.
# This is used to determine the correct compilers to make
# visible to the build environment, installing them if
# necessary. Flags such as --std=c++99 are also added.
# Valid values are: c, c99, c++, c++0x, gnu++0x, c++11, gnu++11,
# c++14, gnu++14, fortran, fortran77, java, objc, obj-c++, and
# ada. The default is "c".
#
# The above is partly aspirational. As an example c++11 does
# not force a new enough version of gcc.
So, USE_LANGUAGE+=c++11 does not translate to gcc>=4.8?
Attachment:
signature.asc
Description: PGP signature