Thanks Mark, but this seems to work only on Redhat 6 and 7 and I’m on RHEL 4.8!!! I made progress with gcc 4.1 but I still get some error later down the line. I’m thinking about compiling static on CentOS 6 and bring the binaries in RHEL 4.8. I’m not too much of a programmer though… Anyone thinks this could work?
Cheers! Pierre De : Oiio-dev [mailto:[email protected]] De la part de Mark Visser Envoyé : 22 juillet 2016 10:16 À : OpenImageIO developers Objet : Re: [Oiio-dev] No atomics on this platform Hi Pierre, It's not obvious, but you can get newer gcc versions for CentOS/RHEL via the devtoolset packages in the scl repo, e.g.: https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/ They install in /opt, so you'll need to either set CC/CXX or use the scl enable command as documented in the link. cheers, -Mark On Thu, Jul 21, 2016 at 3:23 PM, Pierre Guerin <[email protected]<mailto:[email protected]>> wrote: Hi Will, You’re close. Not a Flame but an Arriscan running on a SunFire server. The platform is no longer updated by Arri but it runs just fine. Cheers! Pierre De : Oiio-dev [mailto:[email protected]<mailto:[email protected]>] De la part de Will Rosecrans Envoyé : 20 juillet 2016 19:38 À : OpenImageIO developers Objet : Re: [Oiio-dev] No atomics on this platform Stab in the dark, but are you keeping an old xw8600 Flame alive? You may be able to use your old gcc to install a modern gcc from source if you run out of better ideas. I usually just tried to make sure Flame Ops stuck with classic hardware had access to a "normal" Linux workstations for running non-Flame parts of the internal software stack. An extra workstation usually proved easier than maintaining an RHEL4 port of everything even a few years ago. :/ On Wed, Jul 20, 2016 at 2:22 PM, Pierre Guerin <[email protected]<mailto:[email protected]>> wrote: Hello, I tried to build oiio on RHEL 4.8 on an Opteron 64 bit platform but I get the error « No atomics on this platform » when building OpenImageIO_Util.dir/errorhandler.cpp. Do anyone know what the issue could be? Pierre _______________________________________________ Oiio-dev mailing list [email protected]<mailto:[email protected]> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org _______________________________________________ Oiio-dev mailing list [email protected]<mailto:[email protected]> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
