Menu
▾
▴
[Firebird-checkins] CVS: interbase/firebird/gspeicher/firebird/files RELNOTES,NONE,1.1 patch-aa,NONE,1.1 patch-ab,NONE,1.1 patch-ac,NONE,1.1
|
From: Geoffrey C. S. <gsp...@us...> - 2001-01-14 15:36:49
|
Update of /cvsroot/firebird/interbase/firebird/gspeicher/firebird/files
In directory usw-pr-cvs1:/tmp/cvs-serv5449/gspeicher/firebird/files
Added Files:
RELNOTES patch-aa patch-ab patch-ac
Log Message:
- Here's my own little directory to hold any work that I do that other
people might want to see and/or should be under revision control with
the rest of Firebird in case I get hit by a bus. For now, it just
holds the files from the FreeBSD 'port' (as in, the stuff that was
submitted to the FreeBSD ports tree).
--- NEW FILE ---
Firebird 0.9_4 FreeBSD Release Notes 13-Jan-2001
------------------------------------
FB-T0.9.4.34 Firebird Test1
Welcome to the FreeBSD Firebird port! Users should note that there
was a package called `firebird-1.0.tgz' released in mid-August
2000. Unfortunately, that package was released before Firebird
version numbering conventions were established, so although the
version number would suggest that it is newer than the current
release, it is certainly not. Users of the August 1.0 package
should upgrade to 0.9_4 or later, which has fixed many bugs and
security problems, including the recently-discovered back door.
Firebird originally required a running copy of Firebird (or
InterBase) in order to build itself. This port uses a boot kit to
overcome that, so that it does not require itself to build.
Unfortunately, the side effect of this is that if you have a lock
manager running from an already-installed version of Firebird or
InterBase, this port will not build.
Firebird is installed SUID with owner and group `firebird'.
This does affect where you can and cannot create databases when
connecting remotely, as well as which existing databases you can
access. If you want a database to be available remotely, be sure
it's readable and writeable to group firebird.
There may be times when you manage to get your system into a
state where using any of the Firebird utilites (isql, gbak, gsec,
etc.) gives you the message "semget failed". One surefire way to
do this is to build and install the port. :) If this happens,
make sure that the lock manager is not running and its semaphores
have been removed. The former can be accomplished with 'ps ax
|grep gds' and 'kill'; the latter with 'ipcs -s' and 'ipcrm -s'.
For example, after building and installing the port, you will
probably go through something like this:
# isql /usr/interbase/isc4.gdb
Statement failed, SQLCODE = -902
operating system directive semget failed
-No such file or directory
# ipcs -s
Semaphores:
T ID KEY MODE OWNER GROUP
s 1310720 252034728 --rw-rw-rw- root wheel
# ipcrm -s 1310720
and you should be in business.
Once this is done, you should be able to connect normally to
databases. Your first connection will restart the lock manager.
There may be times, however, when you still get "semget failed"
even though the lock manager is not running and the semaphores have
been cleaned up. There seems to be a conflict with this release
and the PostgreSQL 7 release as installed from the ports collection.
If you're having trouble with Firebird and you're running PostgreSQL,
try stopping PostgreSQL:
/usr/local/etc/rc.d/pgsql.sh stop
and see if that helps.
Complete documentation for InterBase(tm) is available (free of
charge) from http://www.interbase.com/ in PDF format. While
InterBase and Firebird are two distinct entities, all InterBase
documentation is pertinent to Firebird. More information on Firebird
and InterBase can be found at the following:
http://sourceforge.net/projects/firebird/
http://www.ibphoenix.com/
http://www.interbase2000.org/
Geoff Speicher
<ge...@se...>
--- NEW FILE ---
--- buildBootDatabases.orig Tue Oct 10 23:00:39 2000
+++ buildBootDatabases Tue Oct 10 23:00:46 2000
@@ -49,7 +49,7 @@
DefaultAns=$2
echo -n "${1}"
Answer="$DefaultAns"
- read Answer
+# read Answer
}
#--------------------------------------------------------------------
--- NEW FILE ---
--- setup_dirs.boot.orig Tue Oct 10 23:00:07 2000
+++ setup_dirs.boot Tue Oct 10 23:00:22 2000
@@ -49,7 +49,7 @@
DefaultAns=$2
echo -n "${1}"
Answer="$DefaultAns"
- read Answer
+# read Answer
}
--- NEW FILE ---
--- builds/original/prefix.freebsd 2000/10/08 15:36:25 1.2
+++ builds/original/prefix.freebsd 2001/01/11 19:17:58
@@ -28,7 +28,7 @@
PROD_DEBUG_OBJECTS= nodebug.o
-PROD_SHRLIB_DIR=
+PROD_SHRLIB_DIR= -Lsource/jrd
PROD_VERSION_FLAG= -DPROD_BUILD
PROD_CFLAGS= -O -m486 -fpic -DFLINTSTONE
@@ -48,7 +48,7 @@
UDF_LINK_CMD= gcc
UDF_CFLAGS= -fPIC -mieee-fp
UDF_LFLAGS= -shared
-UDF_SHRLIBS= -L/usr/local/lib -lgds -lm -lc -mieee-fp -ldescrypt
+UDF_SHRLIBS= $(SHRLIB_DIR) -lgds -lm -lc -mieee-fp -ldescrypt
#NOTE: PIC_J_CFLAGS is special CFLAGS used to build PIPD_IS_SHRLIB modules
# to workaround the Solaris threading problems with signals
@@ -69,16 +69,14 @@
FUNCTIONS= functions.bin
FUNCSHR= source/interbase/lib/gdsf.so
GDS_LINK= $(GDSSHR_LINK)
-#GDS_PYXIS=
GDS_PYXIS= gds_pyxis.a
GDSLIB_BACKEND= source/interbase/lib/gds_b.a
GDSLIB_LINK= -Lsource/jrd -lgds_b -lc -ldescrypt
GDSSHR= source/interbase/lib/gds.so
LINUX_GDSSHR= $(GDSSHR)
-GDSSHR_LINK= $(SHRLIB_DIR) -L/usr/local/lib -lgds -lgds_pyxis -ldescrypt
-PIPE_GDSSHR_LINK= $(SHRLIB_DIR) -L/usr/local/lib -lgds -lgds_pyxis
-#PIPE_GDSSHR_LINK= $(SHRLIB_DIR) -lgds -lgds_pyxis
+GDSSHR_LINK= $(SHRLIB_DIR) -lgds -lgds_pyxis -ldescrypt
+PIPE_GDSSHR_LINK= $(SHRLIB_DIR) -lgds -lgds_pyxis
HLPDIR= source/qli/
HOSTNAME= `hostname | cut -d'.' -f1`
INCLUDES= include_so include_so_ada
@@ -106,11 +104,6 @@
MUISQL_LINK_OPTS= $(MUISQL_MU_LIB) $(PIPE_GDSSHR_LINK) -lm
PIC_FLAGS= $(CFLAGS) -fPIC
PIPE= gds.a gds_pipe
-#PYXIS=
-#PYXIS_MISC_OBJS=
-#PYXIS_P_MISC_OBJS=
-#PYXIS_OBJECTS=
-#PYXIS_MISC_OBJECTS=
PYXIS= pyxis
PYXIS_MISC_OBJS= $(PYXIS_MISC)
PYXIS_P_MISC_OBJS= $(PYXIS_P_MISC)
@@ -167,5 +160,8 @@
SHRLIB_EXT= .so
V3PRINTER= source/lock/printv3.o
+
+# Forces library build for FreeBSD
+PYXIS_LIBRARY= libpyxis.a
|
