I do have both 2.3 and 2.2... but 2.3 wont build (as I was saying
before) and i last did a 'make install' for 2.2. Yum shows nothing from
the RHEL repos for OpenEXR (which I would expect).
The undef of _ZTIN7Iex_2_27BaseExcE appears to be from IlmIex.so, which
is part of ILMbase, and is an undef for the typeinfo for 'BaseExc'. Why
that should be is a mystery. IlmIex is referenced in 'simd_test.cpp'.
On 4/2/2019 11:37 AM, Colin Doncaster wrote:
It looks like you have multiple OpenEXR versions on your machine? The
one that is being resolved is likely older and missing the required
symbol.
On Apr 2, 2019, at 2:03 PM, Steve Booth <[email protected]
<mailto:[email protected]>> wrote:
Ummmm....
What the heck is 'BaseExcE' and why is it undefined?
<dadijebjfgdkiffm.png>
On 4/2/2019 10:52 AM, Larry Gritz wrote:
Awesome. Truth be told, we're still on OpenEXR 2.2, so I haven't
really run into these problems. It's a little surprising, I still
recommend that you report them to the openexr list.
-- lg
On Apr 2, 2019, at 10:43 AM, Steve Booth <[email protected]
<mailto:[email protected]>> wrote:
Going to 2.2 seems to have fixed the problem. I'm currently
building oiio... will see how it goes. Good to know that option is
available, though. Thanks.
Steve
On 4/2/2019 10:21 AM, Nathan R wrote:
You need to pass `--enable-cxxstd=11` when configuring to build in
c++11 mode. The configure help makes it seem like the standard
will be auto-detected (based on, say, your compiler version), but
in reality it just defaults to 14.
-Nathan
On 4/2/2019 9:58 AM, Steve Booth wrote:
Okay, first for OpenEXR 2.3.0:
I was mistaken. It's not C++17, its C++14. Still...
I mis-typed. I have 4.8, not 4.3:
Which apparently will no longer compile OpenEXR.
On 4/1/2019 10:39 PM, Larry Gritz wrote:
The latest version of OpenEXR requires C++17?
Are you quite sure? I don't think that is true.
On the other hand, gcc 4.3 is long before C++11, so no modern
version of OIIO is expected to work with gcc older than 4.8 and
C++11. That may also be true of OpenEXR, I'm not sure without
checking.
On Apr 1, 2019, at 10:28 PM, Steve Booth <[email protected]
<mailto:[email protected]>> wrote:
I think one of my problems may be that because the latest
version of OpenEXR requires c++17 (gcc7), I ended up with two
different compile environments, since all the other official
repos for my RHEL release (7.4) were compiled under gcc 4.3.
Tomorrow, I'm going to go back and find an OpenEXR version that
compiles under 4.3 and try the whole thing again. Now going on
3 days of solid work just to get it compiled.
Steve
On 4/1/2019 9:26 PM, Larry Gritz wrote:
Opus is not only not a direct dependency of OIIO, but in fact
I'd never heard of it before. (And this is not a build error
we've seen reported before.)
I don't understand... if it's a transitive dependency via
libavcodec, shouldn't it have been automatically installed at
the time that libavcodec was installed or built?
On Apr 1, 2019, at 7:19 PM, Nathan R <[email protected]
<mailto:[email protected]>> wrote:
> But clearly opus needs to be added to the list of dependencies.
The dependency on opus is only a side-effect of the way the
libavcodec you're using was built. Opus should definitely not
be considered a dependency of OIIO.
Luckily, ffmpeg is pretty straightforward to build as a set
of self-contained static libs (I believe it does so by default).
-Nathan
--
Larry Gritz
[email protected] <mailto:[email protected]>
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
*STEVE BOOTH*
PRINCIPAL DEVELOPER @ GO GHOST LLC
BURBANK, CA
Tel: +1 (760) 683 - 4737
[email protected] <mailto:[email protected]>
www.Go-Ghost.com <http://www.go-ghost.com/>
_______________________________________________
Oiio-dev mailing list
[email protected]
<mailto:[email protected]>
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected] <mailto:[email protected]>
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
*STEVE BOOTH*
PRINCIPAL DEVELOPER @ GO GHOST LLC
BURBANK, CA
Tel: +1 (760) 683 - 4737
[email protected] <mailto:[email protected]>
www.Go-Ghost.com <http://www.go-ghost.com/>
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
*STEVE BOOTH*
PRINCIPAL DEVELOPER @ GO GHOST LLC
BURBANK, CA
Tel: +1 (760) 683 - 4737
[email protected] <mailto:[email protected]>
www.Go-Ghost.com <http://www.go-ghost.com/>
_______________________________________________
Oiio-dev mailing list
[email protected] <mailto:[email protected]>
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected] <mailto:[email protected]>
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
*STEVE BOOTH*
PRINCIPAL DEVELOPER @ GO GHOST LLC
BURBANK, CA
Tel: +1 (760) 683 - 4737
[email protected] <mailto:[email protected]>
www.Go-Ghost.com <http://www.go-ghost.com/>
_______________________________________________
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
--
*STEVE BOOTH*
PRINCIPAL DEVELOPER @ GO GHOST LLC
BURBANK, CA
Tel: +1 (760) 683 - 4737
[email protected] <mailto:[email protected]>
www.Go-Ghost.com <http://www.go-ghost.com>
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
