[Top][All Lists]

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

Re: Installation problem on AIX 4.2

From: Thomas Vogels
Subject: Re: Installation problem on AIX 4.2
Date: Wed, 10 Nov 1999 11:51:16 -0500


  one thing to remember when compiling any program for AIX 4.2 (or
4.3) is that you have to use libcurses.a.  There is no termcap or
ncurses.  No surprise it can't find tputs since the linker won't find

  So, yes it's important for configure to detect that it has to use
curses.  Since this is AIX specific (most other platforms I've seen
have ncurses), this is overlooked often.  One hack around this is to
tell configure that there is a local library with "-lcurses".  Or
patch the Makefiles with something close to
"perl -p -i.bak -e 's/-lncurses/-lcurses/' makefile".
Better, fix

  Good luck,

Thomas Ruedas <address@hidden> writes:

> Hello,
> I am trying to install octave 2.0.14 on an IBM RS6000 with AIX 4.2 using
> gcc and c++ (this is /usr/local/gcc/bin/c++) v.2.95.2 and gmake 3.68.
> When running the makefile I got the following error:
> c++ -c  -I. -I.. -I../liboctave -I../src -I../libcruft/misc -I../dlfcn
> -I../dlfcn -I../glob -I../glob -DHAVE_CONFIG_H -mno-fp-in-toc -fno-rtti
> -fno-exceptions -fno-implicit-templates -g -O2 -Wall
> In function `class octave_value_list Fclc(const
> octave_value_list &, int)':
> implicit declaration of function `int tputs(...)'
> gmake[2]: *** [sysdep.o] Error 1
> gmake[2]: Leaving directory `/usr/local/tmp_inst/octave-2.0.14/src'
> gmake[1]: *** [src] Error 1
> gmake[1]: Leaving directory `/usr/local/tmp_inst/octave-2.0.14'
> gmake: *** [all] Error 1
> Configure seemed to be OK, basically, although there are some errors in
> config.log, such as
> configure:5351: checking for tputs in -lncurses
> configure:5370: gcc -o conftest -g -O2  -g conftest.c -lncurses  -lm 

> collect2: Library libncurses not found
> configure: failed program was:
> #line 5359 "configure"
> #include "confdefs.h"
> /* Override any gcc2 internal prototype to avoid an error.  */
> /* We use char because int might match the return type of a gcc2
> builtin and then its argument prototype would still apply.  */
> char tputs();
> int main() {
> tputs()
> ; return 0; }
> configure:5351: checking for tputs in -lcurses
> but I don't know, if this is of any importance.
> I would appreciate any hints on how I can fix this problem. Please cc me
> any replies, as I am not subscribed to this mailing list.
> Thanks in advance,

mailto:address@hidden (Tom Vogels)   Tel: (412) 268-6638   FAX: -3204

Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

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