head	1.9;
access;
symbols
	REL6_4:1.8.0.2
	release-6-3:1.4;
locks; strict;
comment	@# @;


1.9
date	98.12.18.07.08.02;	author momjian;	state dead;
branches;
next	1.8;

1.8
date	98.06.12.22.42.09;	author momjian;	state Exp;
branches;
next	1.7;

1.7
date	98.06.12.22.26.14;	author momjian;	state dead;
branches;
next	1.6;

1.6
date	98.04.27.14.46.37;	author scrappy;	state Exp;
branches;
next	1.5;

1.5
date	98.03.20.03.55.52;	author momjian;	state Exp;
branches;
next	1.4;

1.4
date	97.04.11.18.53.19;	author scrappy;	state Exp;
branches;
next	1.3;

1.3
date	97.04.04.11.22.18;	author scrappy;	state Exp;
branches;
next	1.2;

1.2
date	97.04.04.09.00.43;	author scrappy;	state Exp;
branches;
next	1.1;

1.1
date	97.04.04.07.58.11;	author scrappy;	state Exp;
branches;
next	;


desc
@@


1.9
log
@Attached is a patch with some fixes that (I think that) should go into
6.4.1. Here is the list:

- The type int8 now works. In fact, the bug(s) were in
src/backend/port/snprintf.c, so int8 is probably broken in every platform
that hasn't a native snprintf/vsnprintf. The type itself worked as
expected, only the output was wrong. Anyway, this patch should be checked
in other platforms.

- The regression tests for int2 and int4, which were broken due to
differences in the error messages, are fixed.

- The regression test for float8, which was broken in the reference
platform, is also fixed. I don't know if the new file (float8-OSF1.out)
will work on other platforms, but it might be worth to try it.

- Two new template files are provided (alpha_cc, which includes
optimization, and alpha_gcc), and src/templates/.similar is updated
accordingly. src/templates/alpha should be removed from the distribution.
*IMPORTANT NOTE*: I don't know if you can use gcc to compile postgres;
I've written the alpha_gcc file because alpha_cc has some flags that are
specific to DEC C.

- There is a (very basic) Digital Unix specific FAQ in
doc/FAQ_DigitalUnix.

--
-------------------------------------------------------------------
Pedro Jos Lobo Perea                   Tel:    +34 91 336 78 19
@
text
@AROPT:crs
# NOFIXADE disallows unaligned access.
#   on Ultrix and OSF/1 it invokes an explicit syscall.
#   on HP-UX it turns off certain compiler options.
# This is defined here because a bunch of clients include tmp/c.h,
# which is where the work is done on HP-UX.  It only affects the
# backend on Ultrix and OSF/1.
CFLAGS:-DNOFIXADE
SHARED_LIB:
ALL:
SRCH_INC:
SRCH_LIB:
USE_LOCALE:no
DLSUFFIX:.so
YFLAGS:-d
YACC:
@


1.8
log
@template change
@
text
@@


1.7
log
@template changes
@
text
@@


1.6
log
@From: Ryan Kirkpatrick <rkirkpat@@nag.cs.colorado.edu>

        Ok, I have finally gotten all of the defines for Dec/Alpha and
Linux/Alpha sorted out as Marc asked. There is no longer any need for
'-Dalpha' or '-Dlinuxalpha' in either the Dec/Alpha or the Linux/Alpha
template files (./src/template/{alpha,linuxalpha}). I have replaced every
instance of 'alpha' or '__alpha__' with '__alpha', as that appears to be
the common symbol between C compilers on both operating systems (RH4.2 &
DecUnix 4.0b) for alpha.
@
text
@@


1.5
log
@The real trick is to add -Dalpha to the CFLAGS setting.  The changes
to main.c are only to add some extra includes to support some code
that's suddenly being used.

The #define ASSEMBLER is to prevent most of the code of sys/proc.h
from being included, as it ends up conflicting with some of the
postgresql definitions.  This may or may not work on other versions
of Digital Unix.


Get alpha working.  Yea.  Dwayne Bailey
@
text
@d8 1
a8 1
CFLAGS:-DNOFIXADE -Dalpha
@


1.4
log
@Change BACKEND to CFLAGS
@
text
@d8 1
a8 1
CFLAGS:-DNOFIXADE
@


1.3
log
@Move YACC and YFLAGS into the template files

Clean up the .sample files...comment out all sample entries except for
the localhost one
@
text
@d8 1
a8 1
BACKEND:-DNOFIXADE
@


1.2
log
@Got AROPT setting backwards...correct it
@
text
@d15 2
@


1.1
log
@One helluva mess.

	Further extended Makefile.global/build/configure so that we can
have a 'template' file for each OS (and each version of OS, as in BSDi)
which is used as much as possible to generate Makefile.global

	Any future ports should look at using the template file as a basis,
before moving over to Makefile.global.

	This will most probably break alot of the ports, atho I've tried to
be very neat about it...
@
text
@d1 1
a1 1
AROPT:cq
@
