[RELEASE - head-default] Build failed for trn-4.0.b77 during build

Fri Jul 19 12:28:27 UTC 2013

Maintainer:     johans at FreeBSD.org
Last committer: johans at FreeBSD.org
Ident:          $FreeBSD: head/news/trn4/Makefile 314490 2013-03-17 20:39:10Z johans $
Log URL:        http://beefy1.isc.freebsd.org/bulk/head-default/2013-07-18_22h43m19s/logs/trn-4.0.b77.log
Build URL:      http://beefy1.isc.freebsd.org/bulk/head-default/2013-07-18_22h43m19s
Log:

====>> Building news/trn4
build started at Fri Jul 19 12:28:07 UTC 2013
port directory: /usr/ports/news/trn4
building for: FreeBSD head-default-job-07 10.0-CURRENT FreeBSD 10.0-CURRENT i386
maintained by: johans at FreeBSD.org
Makefile ident:      $FreeBSD: head/news/trn4/Makefile 314490 2013-03-17 20:39:10Z johans $
Poudriere version: 3.1-pre

---Begin Environment---
UNAME_m=i386
UNAME_p=i386
OSVERSION=1000035
UNAME_v=FreeBSD 10.0-CURRENT
UNAME_r=10.0-CURRENT
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
MASTERMNT=/usr/local/poudriere/data/build/head-default/ref
PKG_EXT=txz
FORCE_PACKAGE=yes
tpid=68502
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
POUDRIERE_BUILD_TYPE=bulk
NBPARALLEL=24
PKGNG=1
PKGNAME=trn-4.0.b77
PKG_DELETE=/usr/local/sbin/pkg delete -y -f
PKG_ADD=/usr/local/sbin/pkg add
PWD=/root
MASTERNAME=head-default
USER=root
HOME=/root
POUDRIERE_VERSION=3.1-pre
SKIPSANITY=1
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
---End Environment---

---Begin OPTIONS List---
---End OPTIONS List---

--CONFIGURE_ARGS--

--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
TMPDIR="/tmp" TMPDIR="/tmp" SHELL=/bin/sh CONFIG_SHELL=/bin/sh
--End CONFIGURE_ENV--

--MAKE_ENV--
TMPDIR="/tmp" TMPDIR="/tmp" SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local  LOCALBASE=/usr/local  LIBDIR="/usr/lib"  CC="cc" CFLAGS="-O2 -pipe -fno-strict-aliasing"  CPP="cpp" CPPFLAGS=""  LDFLAGS=""  CXX="c++" CXXFLAGS="-O2 -pipe -fno-strict-aliasing"  MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install  -s -o root -g wheel -m 555"  BSD_INSTALL_LIB="install  -s -o root -g wheel -m 444"  BSD_INSTALL_SCRIPT="install  -o root -g wheel -m 555"  BSD_INSTALL_DATA="install  -o root -g wheel -m 444"  BSD_INSTALL_MAN="install  -o root -g wheel -m 444"
--End MAKE_ENV--

--SUB_LIST--
PREFIX=/usr/local
LOCALBASE=/usr/local
DATADIR=/usr/local/share/trn
DOCSDIR=/usr/local/share/doc/trn
EXAMPLESDIR=/usr/local/share/examples/trn
WWWDIR=/usr/local/www/trn
ETCDIR=/usr/local/etc/trn
--End SUB_LIST--

---Begin make.conf---
ARCH=i386
MACHINE=i386
MACHINE_ARCH=i386
USE_PACKAGE_DEPENDS=yes
BATCH=yes
WRKDIRPREFIX=/wrkdirs
PACKAGES=/packages
DISTDIR=/distfiles
#### /usr/local/etc/poudriere.d/make.conf ####
WITH_PKGNG=yes
NO_RESTRICTED=yes
DISABLE_MAKE_JOBS=yes
---End make.conf---
===>  Cleaning for trn-4.0.b77
=======================<phase: check-config   >============================
=========================================================================
=======================<phase: pkg-depends    >============================
===>   trn-4.0.b77 depends on file: /usr/local/sbin/pkg - not found
===>    Verifying install for /usr/local/sbin/pkg in /usr/ports/ports-mgmt/pkg
===>   Installing existing package /packages/All/pkg-1.1.4_1.txz
Installing pkg-1.1.4_1... done
If you are upgrading from the old package format, first run:

  # pkg2ng
===>   Returning to build of trn-4.0.b77
=========================================================================
=======================<phase: fetch-depends  >============================
=========================================================================
=======================<phase: fetch          >============================
===> Fetching all distfiles required by trn-4.0.b77 for building
=========================================================================
=======================<phase: checksum       >============================
===> Fetching all distfiles required by trn-4.0.b77 for building
=> SHA256 Checksum OK for trn-4.0-test77.tar.gz.
=========================================================================
=======================<phase: extract-depends>============================
=========================================================================
=======================<phase: extract        >============================
===> Fetching all distfiles required by trn-4.0.b77 for building
===>  Extracting for trn-4.0.b77
=> SHA256 Checksum OK for trn-4.0-test77.tar.gz.
=========================================================================
=======================<phase: patch-depends  >============================
=========================================================================
=======================<phase: patch          >============================
===>  Patching for trn-4.0.b77
===>  Applying FreeBSD patches for trn-4.0.b77
=========================================================================
=======================<phase: build-depends  >============================
=========================================================================
=======================<phase: lib-depends    >============================
=========================================================================
=======================<phase: configure      >============================
===>  Configuring for trn-4.0.b77
===>  Running pre-configure target for trn-4.0-test77

Trn comes with a nice Configure script to help you get things setup.
Some of the things this script asks you may be a little misleading.
I (the porter) configured Trn to be as generic as possible.
It assumes a few things.
1. You are accessing news via NNTP, and you set the NNTPSERVER
   environment variable to the name of your news server
2. You have access to the threads databases (either xover or xthread)

You now have three possible choices:

 1) use my configuration as default, run Configure on top of it (recommended).
 2) run Configure from scratch, using trn defaults.
 3) use my defaults and don't do any manual configuration (non-interactive).

Due to a check done iside the Trn Configure script, I cannot run
it automagically.  If you want to pick up the default configura-
tion, simply press ENTER each time the script asks you anything,
EXPECT QUESTION ABOUT USING OLD CONFIG.SH

With either choice, you will want to the the organization to match
your site.  Also you will want to set your distribution codes

Your choice [1]:  
Beginning of configuration questions for trn.

Checking echo to see how to suppress newlines...
..using -n.
The star should be here-->*

First let's make sure your kit is complete.  Checking...
Looks good...

This installation shell script will examine your system and ask you questions
to determine how the trn package should be installed. If you get
stuck on a question, you may use a ! shell escape to start a subshell or
execute a command.  Many of the questions will have default answers in square
brackets; typing carriage return will give you the default.

On some of the questions which ask for file or directory names you are allowed
to use the ~name construct to specify the login directory belonging to "name",
even if you don't have a shell which knows about that.  Questions where this is
allowed will be marked "(~name ok)".

[Type carriage return to continue]  

The prompter used in this script allows you to use shell variables and
backticks in your answers.  You may use $1, $2, etc...  to refer to the words
in the default answer, as if the default line was a set of arguments given to a
script shell.  This means you may also use $* to repeat the whole default line,
so you do not have to re-type everything to add something to the default.

Everytime there is a substitution, you will have to confirm.  If there is an
error (e.g. an unmatched backtick), the default answer will remain unchanged
and you will be prompted again.

If you are in a hurry, you may run 'Configure -d'.  This will bypass nearly all
the questions and use the computed defaults (or the previous answers if there
was already a config.sh file). Type 'Configure -h' for a list of options.
You may also start interactively and then answer '& -d' at any prompt to turn
on the non-interactive behaviour for the remainder of the execution.

[Type carriage return to continue]  

Much effort has been expended to ensure that this shell script will run on any
Unix system.  If despite that it blows up on yours, your best bet is to edit
Configure and run it again.  If you can't run Configure for some reason,
you'll have to generate a config.sh file by hand.  Whatever problems you
have, let me (trn-workers at lists.sourceforge.net) know how I blew it.

This installation script affects things in two ways:

1) it may do direct variable substitutions on some of the files included
   in this kit.
2) it builds a config.h file for inclusion in C programs.  You may edit
   any of these files as the need arises after running this script.

If you make a mistake on a question, there is no easy way to back up to it
<snip>