From owner-freebsd-ports  Wed Jan  6 20:29:34 1999
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA00392
          for freebsd-ports-outgoing; Wed, 6 Jan 1999 20:29:34 -0800 (PST)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00384
          for <ports@freebsd.org>; Wed, 6 Jan 1999 20:29:33 -0800 (PST)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca7-163.ix.netcom.com [209.109.235.163]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id UAA10297 for <ports@freebsd.org>; Wed, 6 Jan 1999 20:29:04 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id UAA41317; Wed, 6 Jan 1999 20:29:00 -0800 (PST)
Date: Wed, 6 Jan 1999 20:29:00 -0800 (PST)
Message-Id: <199901070429.UAA41317@silvia.hip.berkeley.edu>
To: ports@FreeBSD.ORG
Subject: parallel building errors
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi folks,

As many of you have seen in the commit messages, I've committed some
scripts to automatically build packages in parallel.  You can find
them in /usr/ports/Tools/portbuild.

However, some ports don't build for whatever reason.  I put the error
logs from the latest run in

  http://www.freebsd.org/~asami/errorlogs/

if some of you can take a look, that will be great.

There are three things unique to the way this script works.

 @ It uses a fresh chroot dir so it can always start from an empty
   /usr/local and /usr/X11R6.  A port that tries to run "ps" or some
   other stuff can fail becuase of that.

 @ As mentioned above, it starts from an empty /usr/{local,X11R6}.
   Dependencies are automatically installed as packages before the
   build (and DEPENDS_TARGET is set to "/usr/bin/true" so they won't
   be built later).

 @ It uses a read-only /usr/ports (NFS mounted from a central server)
   and WRKDIRPREFIX to build the ports outside the ports tree.  Some
   ports don't work correctly with WRKDIRPREFIX.  Also, there is a
   problem with our NFS that causes totally weird transient errors
   (like it can't cd to a directory that it just created) so ignore
   those.

I have already fixed a lot of ports but I need your help.  If some of
you can take a look at the logs and see if you can figure out what's
going on, that's great.

Thanks!

Satoshi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message