[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C++11 now default?
From: |
Mike Miller |
Subject: |
Re: C++11 now default? |
Date: |
Tue, 23 Feb 2016 17:15:20 -0800 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Tue, Feb 23, 2016 at 12:23:26 -0800, Mike Miller wrote:
> Please try CXX="$CFLAGS -std=gnu++11" only.
Ben, can you pull rev 0705248d47bf and try again without explicitly
specifying any -std= options? I made a change that fixed a problem with
C++11 detection with clang.
> I will try a clang 3.7 (Debian) build today to make sure that still
> works for me.
I made a couple of small fixes and I am able to build the default branch
with clang 3.7 now. Octave segfaults when printing figures for the
manual, but no compiler errors. Many warnings to tackle another day.
--
mike
- Re: C++11 now default?, (continued)
- Re: C++11 now default?, John W. Eaton, 2016/02/22
- Re: C++11 now default?, Mike Miller, 2016/02/22
- Re: C++11 now default?, John W. Eaton, 2016/02/22
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, John W. Eaton, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, Mike Miller, 2016/02/23
- Re: C++11 now default?, Mike Miller, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?,
Mike Miller <=
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, Mike Miller, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, John W. Eaton, 2016/02/24
- Re: C++11 now default?, John W. Eaton, 2016/02/24
- Re: C++11 now default?, Mike Miller, 2016/02/24
- Re: C++11 now default?, John W. Eaton, 2016/02/24
- Re: C++11 now default?, John W. Eaton, 2016/02/25
- Re: C++11 now default?, Ben Abbott, 2016/02/24
- Re: C++11 now default?, Mike Miller, 2016/02/24