Building slony1v2-2.2.2.txz (origin /buildshare/ports/355755/databases/slony1v2) for powerpc-10-0 on XXX slot1: created x distfiles/ x distfiles/slony1-2.2.2-docs.tar.bz2 x distfiles/slony1-2.2.2.tar.bz2 x packages/ x packages/postgresql92-server-9.2.8_1.txz x packages/pkg-1.2.7_2.txz x packages/postgresql92-client-9.2.8_1.txz x packages/help2man-1.43.3_1.txz x packages/perl5-5.16.3_10.txz x packages/libxml2-2.9.1_1.txz x packages/gmake-3.82_1.txz x packages/flex-2.5.39_1.txz x packages/m4-1.4.17_1,1.txz x packages/gettext-0.18.3.1_1.txz x packages/pkgconf-0.9.5.txz x packages/p5-Locale-gettext-1.05_3.txz x packages/bison-2.7.1,1.txz ELF ldconfig path: /lib /usr/lib /usr/lib/compat Make depends ===> slony1v2-2.2.2 depends on file: /usr/local/sbin/pkg - not found ===> Verifying install for /usr/local/sbin/pkg in /buildshare/ports/355755/ports-mgmt/pkg ===> Installing existing package /packages/pkg-1.2.7_2.txz Installing pkg-1.2.7_2... done If you are upgrading from the old package format, first run: # pkg2ng ===> Returning to build of slony1v2-2.2.2 ===> slony1v2-2.2.2 depends on shared library: libpq.so.5 - not found ===> Verifying for libpq.so.5 in /buildshare/ports/355755/databases/postgresql92-client ===> Installing existing package /packages/postgresql92-client-9.2.8_1.txz Installing postgresql92-client-9.2.8_1...Installing gettext-0.18.3.1_1... done Installing libxml2-2.9.1_1... done done The PostgreSQL port has a collection of "side orders": postgresql-docs For all of the html documentation p5-Pg A perl5 API for client access to PostgreSQL databases. postgresql-tcltk If you want tcl/tk client support. postgresql-jdbc For Java JDBC support. postgresql-odbc For client access from unix applications using ODBC as access method. Not needed to access unix PostgreSQL servers from Win32 using ODBC. See below. ruby-postgres, py-PyGreSQL For client access to PostgreSQL databases using the ruby & python languages. postgresql-plperl, postgresql-pltcl & postgresql-plruby For using perl5, tcl & ruby as procedural languages. postgresql-contrib Lots of contributed utilities, postgresql functions and datatypes. There you find pg_standby, pgcrypto and many other cool things. etc... ===> Returning to build of slony1v2-2.2.2 ===> slony1v2-2.2.2 depends on file: /usr/local/bin/flex - not found ===> Verifying install for /usr/local/bin/flex in /buildshare/ports/355755/textproc/flex ===> Installing existing package /packages/flex-2.5.39_1.txz Installing flex-2.5.39_1...Installing m4-1.4.17_1,1... done done ===> Returning to build of slony1v2-2.2.2 ===> slony1v2-2.2.2 depends on file: /usr/local/bin/postmaster - not found ===> Verifying install for /usr/local/bin/postmaster in /buildshare/ports/355755/databases/postgresql92-server ===> Installing existing package /packages/postgresql92-server-9.2.8_1.txz Installing postgresql92-server-9.2.8_1...===> Creating users and/or groups. Creating group 'pgsql' with gid '70'. Creating user 'pgsql' with uid '70'. =========== BACKUP YOUR DATA! ============= As always, backup your data before upgrading. If the upgrade leads to a higher minor revision (e.g. 8.3.x -> 8.4), a dump and restore of all databases is required. This is *NOT* done by the port! Press ctrl-C *now* if you need to pg_dump. =========================================== done For procedural languages and postgresql functions, please note that you might have to update them when updating the server. If you have many tables and many clients running, consider raising kern.maxfiles using sysctl(8), or reconfigure your kernel appropriately. The port is set up to use autovacuum for new databases, but you might also want to vacuum and perhaps backup your database regularly. There is a periodic script, /usr/local/etc/periodic/daily/502.pgsql, that you may find useful. You can use it to backup and perfom vacuum on all databases nightly. Per default, it perfoms `vacuum analyze'. See the script for instructions. For autovacuum settings, please review ~pgsql/data/postgresql.conf. To allow many simultaneous connections to your PostgreSQL server, you should raise the SystemV shared memory limits in your kernel. Here are example values for allowing up to 180 clients (configurations in postgresql.conf also needed, of course): options SYSVSHM options SYSVSEM options SYSVMSG options SHMMAXPGS=65536 options SEMMNI=40 options SEMMNS=240 options SEMUME=40 options SEMMNU=120 If you plan to access your PostgreSQL server using ODBC, please consider running the SQL script /usr/local/share/postgresql/odbc.sql to get the functions required for ODBC compliance. Please note that if you use the rc script, /usr/local/etc/rc.d/postgresql, to initialize the database, unicode (UTF-8) will be used to store character data by default. Set postgresql_initdb_flags or use login.conf settings described below to alter this behaviour. See the start rc script for more info. To set limits, environment stuff like locale and collation and other things, you can set up a class in /etc/login.conf before initializing the database. Add something similar to this to /etc/login.conf: --- postgres:\ :lang=en_US.UTF-8:\ :setenv=LC_COLLATE=C:\ :tc=default: --- and run `cap_mkdb /etc/login.conf'. Then add 'postgresql_class="postgres"' to /etc/rc.conf. ====================================================================== To initialize the database, run /usr/local/etc/rc.d/postgresql initdb You can then start PostgreSQL by running: /usr/local/etc/rc.d/postgresql start For postmaster settings, see ~pgsql/data/postgresql.conf NB. FreeBSD's PostgreSQL port logs to syslog by default See ~pgsql/data/postgresql.conf for more info ====================================================================== To run PostgreSQL at startup, add 'postgresql_enable="YES"' to /etc/rc.conf ===> Returning to build of slony1v2-2.2.2 ===> slony1v2-2.2.2 depends on executable: bison - not found ===> Verifying install for bison in /buildshare/ports/355755/devel/bison ===> Installing existing package /packages/bison-2.7.1,1.txz Installing bison-2.7.1,1... done ===> Returning to build of slony1v2-2.2.2 ===> slony1v2-2.2.2 depends on executable: gmake - not found ===> Verifying install for gmake in /buildshare/ports/355755/devel/gmake ===> Installing existing package /packages/gmake-3.82_1.txz Installing gmake-3.82_1... done ===> Returning to build of slony1v2-2.2.2 Make install ===> slony1v2-2.2.2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by slony1v2-2.2.2 for building ===> Extracting for slony1v2-2.2.2 => SHA256 Checksum OK for slony1-2.2.2.tar.bz2. => SHA256 Checksum OK for slony1-2.2.2-docs.tar.bz2. ===> Patching for slony1v2-2.2.2 ===> slony1v2-2.2.2 depends on file: /usr/local/bin/flex - found ===> slony1v2-2.2.2 depends on file: /usr/local/bin/postmaster - found ===> slony1v2-2.2.2 depends on executable: bison - found ===> slony1v2-2.2.2 depends on executable: gmake - found ===> slony1v2-2.2.2 depends on shared library: libpq.so.5 - found (/usr/local/lib/libpq.so.5) ===> Configuring for slony1v2-2.2.2 ===> FreeBSD 10 autotools fix applied to /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/libtool.m4 ===> FreeBSD 10 autotools fix applied to /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/aclocal.m4 ===> FreeBSD 10 autotools fix applied to /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/configure configure: loading site script /buildshare/ports/355755/Templates/config.site checking build system type... powerpc-portbld-freebsd10.0 checking host system type... powerpc-portbld-freebsd10.0 checking which template to use... freebsd configure: using CFLAGS=-O2 -pipe -fno-strict-aliasing checking for gcc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for perl... no checking for tar... /usr/bin/tar checking for bison... bison -y checking for sed... (cached) /usr/bin/sed checking for the pthreads library -lpthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... -D_THREAD_SAFE checking for cc_r... cc checking how to run the C preprocessor... cpp checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... (cached) /usr/bin/egrep checking for ANSI C header files... (cached) yes checking for sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for memory.h... (cached) yes checking for strings.h... (cached) yes checking for inttypes.h... (cached) yes checking for stdint.h... (cached) yes checking for unistd.h... (cached) yes checking for fcntl.h... (cached) yes checking for limits.h... (cached) yes checking for stddef.h... (cached) yes checking for sys/socket.h... (cached) yes checking for sys/time.h... (cached) yes checking for inttypes.h... (cached) yes checking for gettimeofday... (cached) yes checking for dup2... (cached) yes checking for alarm... (cached) yes checking for memset... (cached) yes checking for select... (cached) yes checking for strdup... (cached) yes checking for strerror... (cached) yes checking for strtol... (cached) yes checking for strtoul... (cached) yes checking for int32_t... (cached) yes checking for uint32_t... yes checking for u_int32_t... (cached) yes checking for int64_t... yes checking for uint64_t... yes checking for u_int64_t... yes checking for size_t... (cached) yes checking for ssize_t... (cached) yes checking for POSIX signal interface... yes checking for flex... /usr/local/bin/flex configure: using flex 2.5.39 checking if you have requested slony1-engine building... yes overriding pgbindir with /usr/local/bin overriding pglibdir with /usr/local/lib overriding pgincludedir with /usr/local/include overriding pgpkglibdir with /usr/local/lib/postgresql overriding pgincludeserverdir with /usr/local/include/postgresql/server overriding pgsharedir with /usr/local/share/postgresql checking for pg_config... /usr/local/bin/pg_config checking for correct version of PostgreSQL... checking for PQunescapeBytea in -lpq... yes checking libpq-fe.h usability... yes checking libpq-fe.h presence... yes checking for libpq-fe.h... yes checking postgres.h usability... yes checking postgres.h presence... yes checking for postgres.h... yes checking for utils/typcache.h... yes checking for plpgsql.so... skipped due to override checking for postgresql.conf.sample... skipped due to override checking for PQputCopyData in -lpq... yes checking for PQsetNoticeReceiver in -lpq... yes checking for PQfreemem in -lpq... yes checking PostgreSQL for thread-safety... PQisthreadsafe() true checking for ScanKeywordLookup... yes, and it takes arguments checking for typenameTypeId... checking for typenameTypeId... yes, and it takes 2 arguments checking for GetActiveSnapshot... yes checking for ScanKeywordLookup... no checking for set_config_option... yes, and it takes arguments yes, and it takes 7 arguments checking for set_config_option... checking for standard_conforming_strings... no checking whether GetTopTransactionId is declared... yes checking for LookupExplicitNamespace 2 args... no checking if you have requested documentation building... no configure: creating ./config.status config.status: creating Makefile.global config.status: creating GNUmakefile config.status: creating slony1.spec config.status: creating Makefile.port config.status: creating config.h ===> Building for slony1v2-2.2.2 gmake[1]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' Using GNU make found at /usr/local/bin/gmake gmake[2]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' gmake[3]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/parsestatements' cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -c -o test-scanner.o test-scanner.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -c -o scanner.o scanner.c cc -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -o test-scanner test-scanner.c scanner.o ./test-scanner < /dev/null > emptytestresult.log ./test-scanner < ./test_sql.sql > test_sql.log ./test-scanner < ./cstylecomments.sql > cstylecomments.log gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/parsestatements' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slon' cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o slon.o slon.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o runtime_config.o runtime_config.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o local_listen.o local_listen.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o remote_listen.o remote_listen.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o remote_worker.o remote_worker.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o sync_thread.o sync_thread.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o monitor_thread.o monitor_thread.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o cleanup_thread.o cleanup_thread.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o scheduler.o scheduler.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o dbutils.o dbutils.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o conf-file.o conf-file.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o confoptions.o confoptions.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -c -o misc.o misc.c cc -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -D_THREAD_SAFE -I../.. -I../../src/slon -o slon slon.o runtime_config.o local_listen.o remote_listen.o remote_worker.o sync_thread.o monitor_thread.o cleanup_thread.o scheduler.o dbutils.o conf-file.o confoptions.o misc.o ../parsestatements/scanner.o -D_THREAD_SAFE -L/usr/local/lib -L/usr/local/lib -lpq -Wl,-R/usr/local/lib -lpthread gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slon' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slonik' cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o slonik.o slonik.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o dbutil.o dbutil.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o parser.o parser.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o scan.o scan.c cc -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" slonik.o dbutil.o parser.o ../parsestatements/scanner.o scan.o -L/usr/local/lib -L/usr/local/lib -lpq -Wl,-R/usr/local/lib -o slonik gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slonik' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/backend' cp ../misc/avl_tree.c avl_tree.c cp ../misc/avl_tree.h avl_tree.h cc -I/usr/local/include -I/usr/local/include/postgresql/server -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -fpic -DPIC -c -o slony1_funcs.o slony1_funcs.c slony1_funcs.c: In function '_Slony_I_2_2_2_logApply': slony1_funcs.c:1000: warning: 'delim_text' may be used uninitialized in this function ld -x -shared -o slony1_funcs.2.2.2.so slony1_funcs.o gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/backend' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/ducttape' gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/ducttape' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slony_logshipper' cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o slony_logshipper.o slony_logshipper.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o dbutil.o dbutil.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o ipcutil.o ipcutil.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o parser.o parser.c cc -I/usr/local/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" -c -o scan.o scan.c cc -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../.. -DPGSHARE="\"/usr/local/share/postgresql\"" slony_logshipper.o dbutil.o ipcutil.o parser.o ../parsestatements/scanner.o scan.o -L/usr/local/lib -L/usr/local/lib -lpq -Wl,-R/usr/local/lib -o slony_logshipper gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slony_logshipper' gmake[3]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src' gmake[3]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools' for subdir in altperl ; do \ /usr/local/bin/gmake -C $subdir all || exit; \ done gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools/altperl' gmake[4]: Nothing to be done for `all'. gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools/altperl' gmake[3]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools' All of Slony-I is successfully made. Ready to install gmake[2]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' gmake[1]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' ===> Staging for slony1v2-2.2.2 ===> Generating temporary packing list gmake[1]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' Using GNU make found at /usr/local/bin/gmake gmake[2]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' gmake[3]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/parsestatements' gmake[4]: Nothing to be done for `install'. gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/parsestatements' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slon' /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/bin /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/install-sh -c -m 755 slon /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/bin gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slon' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slonik' /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/bin /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/install-sh -c -m 755 slonik /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/bin gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slonik' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/backend' /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/lib/postgresql mkdir -p -- /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/lib/postgresql /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/postgresql mkdir -p -- /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/postgresql /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/install-sh -c -m 755 slony1_funcs.2.2.2.so /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/lib/postgresql for file in slony1_base.sql slony1_funcs.sql slony1_base.v83.sql slony1_base.v84.sql slony1_funcs.v83.sql slony1_funcs.v84.sql; do \ /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/install-sh -c -m 644 $file /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/postgresql/`basename $file .sql`.2.2.2.sql || exit ; \ done gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/backend' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/ducttape' /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/ducttape' gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slony_logshipper' /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/bin /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/install-sh -c -m 755 slony_logshipper /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/bin gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src/slony_logshipper' gmake[3]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/src' gmake[3]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools' for subdir in altperl ; do \ /usr/local/bin/gmake -C $subdir install || exit; \ done gmake[4]: Entering directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools/altperl' /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/etc /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/lib /bin/sh /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/config/mkinstalldirs /obj/buildshare/ports/355755/databases/slony1v2/work/stage The altperl tools won't be installed unless --with-perltools is specified in configure gmake[4]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools/altperl' gmake[3]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/tools' All of Slony-I is successfully installed gmake[2]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' gmake[1]: Leaving directory `/obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2' install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/COPYRIGHT /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/INSTALL /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/README /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/README.Unicode /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/RELEASE /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/SAMPLE /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/TODO /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/UPGRADING /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/doc/adminguide/*.html /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/doc/adminguide/*.png /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/share/doc/slony1v2/adminguide/ install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/doc/adminguide/man1/*.1 /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/man/man1 install -o root -g wheel -m 444 /obj/buildshare/ports/355755/databases/slony1v2/work/slony1-2.2.2/doc/adminguide/man7/*.7 /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/man/man7 install -o root -g wheel -m 555 /obj/buildshare/ports/355755/databases/slony1v2/work/slon-mkservice.sh /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/sbin/slon-mkservice install -o root -g wheel -m 444 /buildshare/ports/355755/databases/slony1v2/files/slon.conf-sample /obj/buildshare/ports/355755/databases/slony1v2/work/stage/usr/local/etc ====> Compressing man pages (compress-man) ===> Staging rc.d startup script(s) ===> Installing for slony1v2-2.2.2 ===> Checking if databases/slony1v2 already installed ===> Registering installation for slony1v2-2.2.2 Installing slony1v2-2.2.2... done ******************************************************************************* Please read the docs on configuring and running slony-1. Unless you did not specify the DOCS options, they are in the /usr/local/share/doc/slony1v2 directory. If you are upgrading from a prior version of slony, please read the UPGRADING file in the above docs directory. The script /usr/local/sbin/slon-mkservice can be used to create a control directory to run and monitor the slon daemon under svscan from daemontools. If you use this, be sure not to set slon_enable="YES" in /etc/rc.conf. If you prefer to use the standard startup script in /usr/local/etc/rc.d then set slon_enable="YES" in /etc/rc.conf to enable the slon.sh script. To use either of the above startup configurations, you will need to set up a /usr/local/etc/slon.conf file to tell slon what to replicate. This file is documented in /usr/local/share/doc/slony1/adminguide/runtime-config.html ******************************************************************************* Make package ===> Building package for slony1v2-2.2.2 slot1: removed