Re: Problems compiling 6.5.3 on solaris 2.6 - Mailing list pgsql-ports

From Peter Eisentraut
Subject Re: Problems compiling 6.5.3 on solaris 2.6
Date
Msg-id Pine.LNX.4.21.0007190002360.1545-100000@localhost.localdomain
Whole thread Raw
In response to Problems compiling 6.5.3 on solaris 2.6  ("Ben Reed" <breed@netplexgroup.com>)
List pgsql-ports
Ben Reed writes:

> I'm trying to get postgresql 6.5.3 working on solaris 2.6 with gcc,
> and it's just not cooperating.

Free advice: you really don't want to get it working either. You instead
want to try 7.0.2. ;-)

> checking for ANSI C header files... grep: can't open conftest.out
> no

I gotta hand it to those guys: very informative error message. The shell
code looks like this:

| ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
| { (eval echo configure:3273: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
| ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`

which should surely create a conftest.out file.

> gcc -I../../../include -I../../../backend    -Wall -Wmissing-prototypes -I..
> /..    -c -o istrat.o istrat.c
> istrat.c: In function `OperatorRelationFillScanKeyEntry':
> istrat.c:492: `F_OIDEQ' undeclared (first use in this function)

> Any ideas what should be defining F_OIDEQ?

Yup, it should be in backend/utils/fmgr.h. That file is created from a
bunch of other files, and I don't think this is the first time Solaris awk
or similar would have balked. If you want to investigate further you could
go into backend/utils and try to run the commands by hand somehow, but it
seems to me that your whole system is somehow in a shaky
state. (PATH? shared libraries? umask?, ...)


--
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


pgsql-ports by date:

Previous
From: "luc00"
Date:
Subject: self Installing Kit for win2000 ?
Next
From: David Wetzel
Date:
Subject: which type matches Oracle's NUMBER type best?