<div dir="auto">Several arguments are contained in this thread.</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Feb 5, 2019, 2:15 PM Robert Maynard <<a href="mailto:robert.maynard@kitware.com">robert.maynard@kitware.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If RHEL8 comes I could see us dropping support for GCC 4.8, as RHEL7<br>
with dev-tools can be used, or RHE8.<br>
<br>
Either way, somebody needs to make official arguments on when/why we<br>
should drop gcc 4.8.<br>
<br>
On Tue, Feb 5, 2019 at 5:06 PM Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com" target="_blank" rel="noreferrer">bill.lorensen@gmail.com</a>> wrote:<br>
><br>
> I have no objections, never did. At least it forced me to update to gcc 8.2.<br>
><br>
> If 4.8.5 is supported Kitware should have a dashboard for it.<br>
><br>
> Red Hat 7.6 support and Ocyober 31, 2020. So I guess we'll support it until then.<br>
><br>
><br>
> On Tue, Feb 5, 2019, 1:50 PM Sankhesh Jhaveri <<a href="mailto:sankhesh.jhaveri@kitware.com" target="_blank" rel="noreferrer">sankhesh.jhaveri@kitware.com</a> wrote:<br>
>><br>
>> Hi Bill,<br>
>><br>
>> I don’t know why the minimum supported version is v4.8.3. However, the issue we have is with v4.8.5 which is the default compiler on the latest Red Hat OS (See <a href="https://access.redhat.com/solutions/19458" rel="noreferrer noreferrer" target="_blank">https://access.redhat.com/solutions/19458</a> ); which merits maintaining support for it. Do you concur?<br>
>><br>
>> Best,<br>
>> Sankhesh<br>
>><br>
>><br>
>> On Tue, Feb 5, 2019 at 4:40 PM Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com" target="_blank" rel="noreferrer">bill.lorensen@gmail.com</a>> wrote:<br>
>>><br>
>>> I saw the MR. My question is why are we supporting an old compiler. I think that's what the argument against my first post in this thread.<br>
>>><br>
>>> On Tue, Feb 5, 2019, 1:34 PM Sankhesh Jhaveri <<a href="mailto:sankhesh.jhaveri@kitware.com" target="_blank" rel="noreferrer">sankhesh.jhaveri@kitware.com</a> wrote:<br>
>>>><br>
>>>> FWIW, I have a MR here: <a href="https://gitlab.kitware.com/vtk/vtk/merge_requests/5157" rel="noreferrer noreferrer" target="_blank">https://gitlab.kitware.com/vtk/vtk/merge_requests/5157</a><br>
>>>><br>
>>>><br>
>>>> On Tue, Feb 5, 2019 at 4:32 PM Robert Maynard <<a href="mailto:robert.maynard@kitware.com" target="_blank" rel="noreferrer">robert.maynard@kitware.com</a>> wrote:<br>
>>>>><br>
>>>>> I meant GCC 4.8.3/5 is a supported compiler by VTK not GCC itself.<br>
>>>>><br>
>>>>> On Tue, Feb 5, 2019 at 4:29 PM Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com" target="_blank" rel="noreferrer">bill.lorensen@gmail.com</a>> wrote:<br>
>>>>> ><br>
>>>>> > Gcc 4.8 is no longer maintained. See<br>
>>>>> > <a href="https://www.gnu.org/software/gcc/gcc-4.8/" rel="noreferrer noreferrer" target="_blank">https://www.gnu.org/software/gcc/gcc-4.8/</a><br>
>>>>> ><br>
>>>>> ><br>
>>>>> ><br>
>>>>> > On Tue, Feb 5, 2019, 1:27 PM Robert Maynard <<a href="mailto:robert.maynard@kitware.com" target="_blank" rel="noreferrer">robert.maynard@kitware.com</a> wrote:<br>
>>>>> >><br>
>>>>> >> I wasn't paying attention to the thread. GCC 4.8.3 is a supported<br>
>>>>> >> compiler and until we remove it we have to accept that we need to<br>
>>>>> >> support it.<br>
>>>>> >><br>
>>>>> >> On Tue, Feb 5, 2019 at 4:21 PM Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com" target="_blank" rel="noreferrer">bill.lorensen@gmail.com</a>> wrote:<br>
>>>>> >> ><br>
>>>>> >> > What happened to the arguments against my complaints about this error?<br>
>>>>> >> ><br>
>>>>> >> > Bill<br>
>>>>> >> ><br>
>>>>> >> > On Tue, Feb 5, 2019, 9:23 AM Sankhesh Jhaveri <<a href="mailto:sankhesh.jhaveri@kitware.com" target="_blank" rel="noreferrer">sankhesh.jhaveri@kitware.com</a> wrote:<br>
>>>>> >> >><br>
>>>>> >> >> Sweet, thanks Rob,<br>
>>>>> >> >><br>
>>>>> >> >><br>
>>>>> >> >> On Tue, Feb 5, 2019 at 11:31 AM Robert Maynard <<a href="mailto:robert.maynard@kitware.com" target="_blank" rel="noreferrer">robert.maynard@kitware.com</a>> wrote:<br>
>>>>> >> >>><br>
>>>>> >> >>> Here is a drop-in wrapper for rotate that has the C++11 behavior but<br>
>>>>> >> >>> also works with GCC 4.8 ( <a href="https://godbolt.org/z/1aVjiZ" rel="noreferrer noreferrer" target="_blank">https://godbolt.org/z/1aVjiZ</a> ).<br>
>>>>> >> >>><br>
>>>>> >> >>> On Tue, Feb 5, 2019 at 10:29 AM Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com" target="_blank" rel="noreferrer">bill.lorensen@gmail.com</a>> wrote:<br>
>>>>> >> >>> ><br>
>>>>> >> >>> > I don't have a fix. Best if you can look.<br>
>>>>> >> >>> ><br>
>>>>> >> >>> > I've built gcc 8.2 do I don't have a problem.<br>
>>>>> >> >>> ><br>
>>>>> >> >>> > Bill<br>
>>>>> >> >>> ><br>
>>>>> >> >>> > On Tue, Feb 5, 2019, 7:20 AM Sankhesh Jhaveri <<a href="mailto:sankhesh.jhaveri@kitware.com" target="_blank" rel="noreferrer">sankhesh.jhaveri@kitware.com</a> wrote:<br>
>>>>> >> >>> >><br>
>>>>> >> >>> >> Bill,<br>
>>>>> >> >>> >><br>
>>>>> >> >>> >> It would be great if you have a fix, neverthless. A customer noticed the same issue on Red Hat GCC v4.8.5 20150623. The README says VTK requires gcc v4.8.3 or newer.<br>
>>>>> >> >>> >><br>
>>>>> >> >>> >> Let me know if you would rather I look into a fix for it.<br>
>>>>> >> >>> >><br>
>>>>> >> >>> >> Thanks,<br>
>>>>> >> >>> >> Sankhesh<br>
>>>>> >> >>> >><br>
>>>>> >> >>> >><br>
>>>>> >> >>> >> On Tue, Feb 5, 2019 at 1:27 AM Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com" target="_blank" rel="noreferrer">bill.lorensen@gmail.com</a>> wrote:<br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> Sean,<br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> Thanks for the suggestion. I was able to build gcc 8.2 on my Ubuntu<br>
>>>>> >> >>> >>> 14.04 system. Only a little tricky. Took several hours to compile.<br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> I have successfully built VTK HEAD and the VTKExamples. All VTK tests passed.<br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> No more bitching from me (about this topic anyway0><br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> The compiler did expose some new warnings which I'll fix.<br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> Bill<br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> On Mon, Feb 4, 2019 at 8:38 AM Sean McBride <<a href="mailto:sean@rogue-research.com" target="_blank" rel="noreferrer">sean@rogue-research.com</a>> wrote:<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > On Thu, 31 Jan 2019 20:37:32 -0500, David Thompson via vtk-developers said:<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > >I'm not sure it is a good idea to support old compilers and distributions:<br>
>>>>> >> >>> >>> > ><br>
>>>>> >> >>> >>> > >1. Ubuntu 14.04 LTS will lose support from Canonical in 3 months. I<br>
>>>>> >> >>> >>> > >would be surprised if what is in git master is released by then. Why<br>
>>>>> >> >>> >>> > >should we support platforms no longer supported by their distributor?<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > Is the compiler so tied to the OS? Bill, can't you upgrade your compiler without updating your whole OS?<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > >2. If we keep forcing workarounds, the next time something breaks, then<br>
>>>>> >> >>> >>> > >*it* will be the only compiler error. That pattern just keeps accruing<br>
>>>>> >> >>> >>> > >technical debt. Ultimately, I believe that technical debt will push<br>
>>>>> >> >>> >>> > >developers away from VTK so I want to avoid it.<br>
>>>>> >> >>> >>> > ><br>
>>>>> >> >>> >>> > >3. Not too long ago, it was common practice for systems in production<br>
>>>>> >> >>> >>> > >use to never get patched (lest the patch break what was working).<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > Not that we (programmers collectively) have solved the problem of patches always breaking things that work. It's still the norm. :(<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > >However, security issues and increased connectivity prevalent today has<br>
>>>>> >> >>> >>> > >pretty much put a stop to this practice and I think that translates into<br>
>>>>> >> >>> >>> > >a much weaker argument for supporting older systems.<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > I largely agree, but there are exceptions.<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > Perhaps less on linux, but newer versions of macOS often drop support for older hardware. So it's not always easy or cheap to just keep all software up-to-date.<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > Cheers,<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> > --<br>
>>>>> >> >>> >>> > Sean<br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>> ><br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> --<br>
>>>>> >> >>> >>> Unpaid intern in BillsParadise at noware dot com<br>
>>>>> >> >>> >>> _______________________________________________<br>
>>>>> >> >>> >>> Powered by <a href="http://www.kitware.com" rel="noreferrer noreferrer" target="_blank">www.kitware.com</a><br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> Search the list archives at: <a href="http://markmail.org/search/?q=vtk-developers" rel="noreferrer noreferrer" target="_blank">http://markmail.org/search/?q=vtk-developers</a><br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >>> Follow this link to subscribe/unsubscribe:<br>
>>>>> >> >>> >>> <a href="https://vtk.org/mailman/listinfo/vtk-developers" rel="noreferrer noreferrer" target="_blank">https://vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>> >> >>> >>><br>
>>>>> >> >>> >> --<br>
>>>>> >> >>> >><br>
>>>>> >> >>> >> Sankhesh Jhaveri<br>
>>>>> >> >>> >><br>
>>>>> >> >>> >> Sr. Research & Development Engineer | Kitware | (518) 881-4417<br>
>>>>> >> >>> ><br>
>>>>> >> >>> > _______________________________________________<br>
>>>>> >> >>> > Powered by <a href="http://www.kitware.com" rel="noreferrer noreferrer" target="_blank">www.kitware.com</a><br>
>>>>> >> >>> ><br>
>>>>> >> >>> > Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>> >> >>> ><br>
>>>>> >> >>> > Search the list archives at: <a href="http://markmail.org/search/?q=vtk-developers" rel="noreferrer noreferrer" target="_blank">http://markmail.org/search/?q=vtk-developers</a><br>
>>>>> >> >>> ><br>
>>>>> >> >>> > Follow this link to subscribe/unsubscribe:<br>
>>>>> >> >>> > <a href="https://vtk.org/mailman/listinfo/vtk-developers" rel="noreferrer noreferrer" target="_blank">https://vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>> >> >>> ><br>
>>>>> >> >><br>
>>>>> >> >> --<br>
>>>>> >> >><br>
>>>>> >> >> Sankhesh Jhaveri<br>
>>>>> >> >><br>
>>>>> >> >> Sr. Research & Development Engineer | Kitware | (518) 881-4417<br>
>>>><br>
>>>> --<br>
>>>><br>
>>>> Sankhesh Jhaveri<br>
>>>><br>
>>>> Sr. Research & Development Engineer | Kitware | (518) 881-4417<br>
>><br>
>> --<br>
>><br>
>> Sankhesh Jhaveri<br>
>><br>
>> Sr. Research & Development Engineer | Kitware | (518) 881-4417<br>
</blockquote></div>