Skip to content

Conversation

@Teemperor
Copy link
Contributor

libOracle.so is compiled with stdc++ and on OS X we're always
compiling with libc++. To prevent linking errors between libOracle.so
and the generated ROOT code in the STL symbols, we just disable
Oracle on this platform.

libOracle.so is compiled with stdc++ and on OS X we're always
compiling with libc++. To prevent linking errors between libOracle.so
and the generated ROOT code in the STL symbols, we just disable
Oracle on this platform.
@Teemperor
Copy link
Contributor Author

See for example #562 for something that is affected by this.

message(WARNING "Oracle not supported when compiling with libc++!")
set(oracle OFF CACHE BOOL "" FORCE)
endif()

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are assuming that oracle will never deliver libraries for libc++. Can we not at this moment disable the oracle option -Doracle=OFF for the current state of the externals we use.

@peremato
Copy link
Contributor

It would be sufficient to disable oracle for this build of ROOT using these set of externals. I would not change the code for this.

@pcanal
Copy link
Member

pcanal commented May 10, 2017

Shouldn't we do that in jenkins instead? I.e. This does not check if the oracle library found has been compiled with one library or the other (so once/when there is a oracle library using libcxx this test will be wrong).

@Teemperor Teemperor closed this May 10, 2017
@Teemperor Teemperor deleted the SkipIncompatibleOracle branch May 10, 2017 14:47
@Axel-Naumann
Copy link
Member

Plus (for the record) there are people building ROOT on MacOS with GCC, even successfully so. They could use the default libocci.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants