Re: [BUGS] Before I call it a bug - some comments and questions

2010-09-14 Thread Michael Felt
Guess this means no further suggestions. I'll hack at it then. On Fri, Sep 10, 2010 at 2:26 PM, Michael Felt wrote: > Tom and Chris - thank you for your answers. There are several reasons for > not including /usr/local/include. Some of those reasons are that I do not > want to be adding files to

Re: [BUGS] Before I call it a bug - some comments and questions

2010-09-10 Thread Michael Felt
Tom and Chris - thank you for your answers. There are several reasons for not including /usr/local/include. Some of those reasons are that I do not want to be adding files to /usr/include - when it concerns dependencies I have had to build before getting started. But that is my choice. No further c

Re: [BUGS] Before I call it a bug - some comments and questions

2010-09-09 Thread Chris Browne
mamf...@gmail.com (Michael Felt) writes: > I have just run compiled postgres on AIX (AIX 5.3, pgsql version 8.4.4) and > have a few surprises regarding the make process. > > 1. Very nice - it found gmake as /usr/local/bin/make and called GNUmakefile > 2. The make completes and it starts a test. > -

Re: [BUGS] Before I call it a bug - some comments and questions

2010-09-09 Thread Tom Lane
Michael Felt writes: > -- As I build, generally, as root - this failed because initdb does not want > to run as root Many people regard that as bad practice ... > --- why is the initial make installing/copying anything outside of the > project directory (in this case it was /usr/local/pgsql if I

[BUGS] Before I call it a bug - some comments and questions

2010-09-09 Thread Michael Felt
I have just run compiled postgres on AIX (AIX 5.3, pgsql version 8.4.4) and have a few surprises regarding the make process. 1. Very nice - it found gmake as /usr/local/bin/make and called GNUmakefile 2. The make completes and it starts a test. -- As I build, generally, as root - this failed becau