[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C++11 now default?
From: |
Ben Abbott |
Subject: |
Re: C++11 now default? |
Date: |
Wed, 24 Feb 2016 10:33:07 -0500 |
> On Feb 23, 2016, at 20:15, Mike Miller <address@hidden> wrote:
>
> 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.
I'm also seeing segfaults when printing figures for the manual. I thought this
was another Mac problem, so I hadn't mentioned it. The segfaults are
reproducible, so if I run make several times, the manual eventually completed.
Also, I don't have Omesa, so my crashes occur with GNUPLOT.
Ben
- Re: C++11 now default?, (continued)
- 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?, 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 <=
- Re: C++11 now default?, Mike Miller, 2016/02/24
- Re: C++11 now default?, Ben Abbott, 2016/02/24
- Re: C++11 now default?, Mike Miller, 2016/02/23
Re: C++11 now default?, John W. Eaton, 2016/02/25
Re: C++11 now default?, Rik, 2016/02/23