[petsc-dev] My configure is non-working again because of CMake
Jed Brown
jed at jedbrown.org
Thu Jul 5 17:36:02 CDT 2018
Matt, you're gonna have to upgrade your compiler eventually. You can
postpone it a few months or perhaps a year.
Satish Balay <balay at mcs.anl.gov> writes:
> Well - can you find the version between 3.7 and 3.11 that works on your box?
>
> The previous update was done due to:
> https://bitbucket.org/petsc/petsc/commits/e5b329dd4ac
>
> No point in going back to having old issues..
>
> Satish
>
> On Thu, 5 Jul 2018, Matthew Knepley wrote:
>
>> On Thu, Jul 5, 2018 at 5:18 PM Satish Balay <balay at mcs.anl.gov> wrote:
>>
>> > Logs?
>> >
>>
>> I can send it, but its really straightforward. The clang++/g++ on my box
>> (which I will not upgrade because the latest MacOS is crazy)
>> does not have the <unorderedset> header, and thus is not compliant C++11.
>>
>>
>> > And what version of cmake does not require C++11 compliant compiler? We
>> > could downgrade to that..
>> >
>>
>> I reverted back to 3.7 which worked, so somewhere in between 3.7 and 3.11
>> they made the change.
>>
>> Thanks,
>>
>> Matt
>>
>>
>> > Satish
>> >
>> > On Thu, 5 Jul 2018, Matthew Knepley wrote:
>> >
>> > > Now we require a fully C++11 compliant compiler, or the CMake build dies.
>> > > This is crazy.
>> > >
>> > > Matt
>> > >
>> > >
>> >
>> >
>>
>>
More information about the petsc-dev
mailing list