1st build attempt failed on rawhide (both i386/x86_64) and I found out
-std=gnu++11 was present in compiling flags (we requested -std=c++11).

Then someone in #fedora-qa pointed me out to this bug report:

 https://forum.qt.io/topic/69057/where-std-gnu-11-came-from/3

2nd build attempt was just a workaround trying to fix compilation when
-std=gnu++11 is present (so the -fext-numeric-literals flag), this time
build failed on rawhide x86_64.

The right fix is setting required language standard in cmake as I did (
SET(CMAKE_CXX_STANDARD 11) ),
This time build succeeds on each fedora version (and -std=gnu++11 is used).


Thank you
Franco

On 29 August 2016 at 15:23, Jakub Jelinek <ja...@redhat.com> wrote:

> On Mon, Aug 29, 2016 at 02:08:10PM +0100, Jonathan Wakely wrote:
> > >https://copr-be.cloud.fedoraproject.org/results/
> fcomida/LuminanceHDR-SNAPSHOT/fedora-rawhide-x86_64/
> 00446298-luminance-hdr/build.log.gz
> > >
> > >The pulling in of -std=gnu++11 in rawhide should be fixed anyway
> >
> > Nothing in rawhide adds that flag automatically, it must be your
> > package.
>
> Well, -std=gnu++14 is the default in GCC 6+, so if you don't pass any -std=
> options, that is what you get.
>
>         Jakub
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Reply via email to