From owner-freebsd-ports  Wed Jul 19 04:38:02 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id EAA20405
          for ports-outgoing; Wed, 19 Jul 1995 04:38:02 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id EAA20399
          for <ports@freefall.cdrom.com>; Wed, 19 Jul 1995 04:38:00 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id EAA01782; Wed, 19 Jul 1995 04:37:45 -0700
Date: Wed, 19 Jul 1995 04:37:45 -0700
Message-Id: <199507191137.EAA01782@silvia.HIP.Berkeley.EDU>
To: werner@btp1da.phy.uni-bayreuth.de
CC: ports@freefall.cdrom.com
In-reply-to: <199507191001.MAA02265@btp1da.phy.uni-bayreuth.de> (message from Werner Griessl on Wed, 19 Jul 1995 12:01:09 +0200 (MET DST))
Subject: Re: fwf-install-broken
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: ports-owner@FreeBSD.org
Precedence: bulk

 * ldconfig -m /usr/X11R6/lib
 * ldconfig: illegal option -- m
 * Usage: ldconfig [-r][-s][-v][dir ...]
 * *** Error code 1

This is because the ports tree is under -current jurisdiction.  The
new option "-m" of ldconfig was added after 2.0.5R went out.

If you are running 2.0.5R, you should probably stick to ports-2.0.5.
But of course, FWF wasn't in ports-2.0.5. ;>

Satoshi

P.S. The particular offending line has just been taken out, by the
     way...it's for ports that install shared libraries, and FWF is
     not one of them.