Hi!
Jon Earle wrote:
> Hi all!
>
> I'm having trouble building the latest stable on AIX 5.1. My env is as follows:
>
> Relevant GNU tools:
>
> [[...]]
> gcc-3.3.2-4.aix5.1.ppc.rpm
> [[...]]
I admit I did not use gcc on AIX for quite some time.
>
> Results in the following error:
>
> ...
> checking term.h usability... no
> checking term.h presence... yes
> configure: WARNING: term.h: present but cannot be compiled
> configure: WARNING: term.h: check for missing prerequisite headers?
> configure: WARNING: term.h: see the Autoconf documentation
> configure: WARNING: term.h: section "Present But Cannot Be Compiled"
> configure: WARNING: term.h: proceeding with the preprocessor's result
> configure: WARNING: term.h: in the future, the compiler will take precedence
> configure: WARNING: ## ------------------------------------------ ##
> configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ##
> configure: WARNING: ## ------------------------------------------ ##
> checking for term.h... yes
Still, this seems to be a problem with the header files supplied / used
by gcc. Are you sure you used the "fixincludes" script?
> ...
>
> config.log has this to say on that:
>
> ...
> configure:22525: checking term.h usability
> configure:22537: gcc -c -mcpu=powerpc -Wa,-many conftest.c >&5
> In file included from conftest.c:90:
> /usr/include/term.h:1194: error: parse error before "bool"
> /usr/include/term.h:1225: error: parse error before "SGTTY"
> [[...]]
IMO, this points into the same direction.
Other than that, I have no idea. Double-check / repeat "fixincludes".
If all else fails, I propose you check (the archives of) the
"comp.unix.aix" newgroup.
>
> [[...]]
>
> As of now, I believe my Qs are:
>
> 1. What is the correct usage of curses, term and termcap? Which do I need?
> And why don't the MySQL folks run into this problem - what's their AIX 5.1
> environment like that gives them a smooth compilation?
On AIX, we use IBM's compiler.
>
> 2. The docs say that using CXX=gcc (to use gcc as a c++ compiler) is
> preferable. Why does it seem to fail for me, forcing me to using the true
> g++ compiler?
AFAIK, the main difference between "gcc" and "g++" ist the list of
libraries included by default when the compiler acts as a front-end to
the linker. Your problems seem to occur in earlier stages.
HTH,
Jörg