Thanks to everyone for giving me a starting point. 

here's what I tried so far:
changed the CFLAGS in the src/template/freebsd file to:
CFLAGS='-O0 -pipe'

did
./configure --with-template=freebsd

configure succeeded.

Did a make and started to build.  During the build, there were a ton of messages of 
this type:
../../../../src/include/catalog/pg_type.h:414: stray '\' in program

make exited with this:

cc -c  -I../../../src/include  -O0 -pipe -Wall -Wmissing-prototypes 
-Wmissing-declarations -o dynloader.o dynloader.c
dynloader.c:42: header file 'link.h' not found
dynloader.c:43: header file 'dlfcn.h' not found
../../../src/include/dynloader.h:19: header file 'link.h' not found
make[3]: *** [dynloader.o] Error 1
make[2]: *** [port-recursive] Error 2
make[1]: *** [all] Error 2
make: *** [all] Error 2


Not sure if configure didn't move the correct files or if there was something else 
wrong.  I was using the lastest developer snapshot for testing.  I also tried it on a 
stock 7.0.2 source but got the same error.

Any ideas?  I'm willing to try and get this working but unfortunately my grasp of the  
process is pretty weak.  

Mike


On Friday, October 13, 2000, at 11:42 PM, Tom Lane wrote:

Michael Engelhart <[EMAIL PROTECTED]> writes:
> Thanks Adam.  Yeah, I know that it uses a mach kernel and variant of
> freebsd runs atop the kernel.  I would attempt the FreeBSD template
> but the other snag is that it has to compile on PowerPC.

FreeBSD template seems like it'd be a good starting point.  7.0.*
will probably not work on PPC unless you compile with optimization
level -O0, so tweak CFLAGS in the template that way before running
configure.  Otherwise it seems like it'd more or less work --- give
it a shot and let us know how it goes.

BTW, I think the PPC optimization issues are solved in current sources.
>From a development perspective it'd be more interesting to hear your
report on what happens with a current nightly snapshot instead of 7.0.2.

                regards, tom "didn't order my OS X yet :-(" lane

Reply via email to