[Octave-bug-tracker] [bug #33018] ./configure considered broken

[John W. Eaton]

Follow-up Comment #3, bug #33018 (project octave):

The configure script uses the compiler to check for amd.h using the following
names


suitesparse/amd.h
ufsparse/amd.h
amd/amd.h
amd.h


so if you have amd.h installed in /app/include, setting
CPPFLAGS=-I/app/include should allow the compiler to find it.

I have no way of helping you find out why that is not working properly for you
if you only tell me that it doesn't work/can't work/didn't work/whatever.  You
will have to show precisely what is going wrong by posting the relevant parts
of the config.log file.

GCC 3.4.3 is indeed too old to build Octave.  But that release is over 6 years
old now.  That is absolutely ancient in the history of GCC and in particular
its support for modern C++, so it is not surprising at all to me that it does
not work.  If you want to build Octave, you are going to have to use somewhat
modern tools.  Sorry.

You wrote:


I have observed that pieces get added to liboctinterp using a libtool
executable link procedure which is not valid on Solaris for shared libraries.


I have no idea what you mean by this.  If you want help debugging the problem,
you need to post precisely what you have done and precisely the error messages
that you are seeing.

I suggest you try the following to build a minimal version of Octave:

* unpack a fresh copy of Octave
* execute the configure script with just ./configure
* run make

If the configure script fails, post details about the specific failure.

If make fails, post details about the specific failure.


    _______________________________________________________

Reply to this item at:

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

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