[Octave-bug-tracker] [bug #41061] Octave fails to build with LLVM 3.5

[Michael Godfrey]

Follow-up Comment #34, bug #41061 (project octave):

Jordi:  As you point out, this is not a happy
situation. Someday, RHEL may move up, but I would
not hold my breath. They are VERY "conservative."
And, to make matters worse, many major sites are one
or two levels behind the current release of RHEL.
For a large production site, moving up is a very major
effort. It would be helpful to continue to provide
Octave that they can use.

However, note that the default for LLVM is to NOT
attempt to include it.  Only ./configure --enable-jit
attempts to turn it on. So, I see no need to remove
the, normally unused, code.

So, obviously, the recent patch should not be applied
in its present form or probably not at all. 

This should be preserved in case someone shows up to
put serious work into the implementation.

On the brighter side, I was surprised that the current
system does compile "correctly" using C++11. The various
warnings do not apparently prevent it from generating 
correct code.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41061>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/