octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54235] problems building Octave on Solaris


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #54235] problems building Octave on Solaris
Date: Mon, 16 Jul 2018 15:11:22 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Follow-up Comment #119, bug #54235 (project octave):

Here is my best attempt at a summary of the various issues here, including the
things that I had Michele patch out of the build.

Only points 2 and 3 below have to do with the Octave source itself, the rest
are entirely system configuration issues.

1. Automake assumes the 'id' program will be POSIX compliant, Michele has
moved the Solaris 'id' program out of the way and symlinked 'gid' so that 'id'
is now GNU. This was more of a visual annoyance than a fatal error, it is only
needed for Automake to know how to build a tar file for 'make dist'.

2. bug #53853 - the configure test for BLAS integer size only works on little
endian machines, the sed command in comment #115 works around that by forcing
the test to declare the integer size is 4 bytes.

3. bug #54237 - the 'abs' local function template in pr-output.cc has problems
with some interaction with the Solaris system and C++ header files with GCC
4.9.2. I do not see these problems with GCC 4.8 on an Ubuntu system, so it is
not just the compiler version. At the moment I am assuming a newer compiler
might fix this, or that we will rework this hack in pr-output.cc at some
point.

4. The freetype.pc pkg-config configuration on Michele's system is somehow
mixing or confusing /usr/sfw and /opt/csw. All other development packages
installed in /opt/csw are only linking with libraries in /opt/csw. When
/usr/sfw/lib is pulled in by freetype.pc, the build tries to link with two
different instances of libstdc++.so and libgomp.so (comment #78).

5. The GraphicsMagick package available from OpenCSW was built with GCC 5 and
using GCC's new C++11 ABI. Therefore the symbol table is not compatible with
GCC 4.9.2 and cannot be linked in with this build (comment #65).

6. The OpenGL header files on this system seemed to have some missing type
problems that I don't understand (comment #52).

7. Upgrading to GCC 5 seemed to be a disaster, the g++ 5 compiler was unable
to compile a very trivial C++11 program at all with the '-std=gnu++11' option
(comment #32).

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]