From owner-freebsd-current  Fri Aug 22 14:28:11 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA03126
          for current-outgoing; Fri, 22 Aug 1997 14:28:11 -0700 (PDT)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA03120;
          Fri, 22 Aug 1997 14:28:05 -0700 (PDT)
Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.6/8.7.3) id OAA11160; Fri, 22 Aug 1997 14:27:31 -0700 (PDT)
Date: Fri, 22 Aug 1997 14:27:31 -0700 (PDT)
Message-Id: <199708222127.OAA11160@vader.cs.berkeley.edu>
To: gurney_j@resnet.uoregon.edu
CC: current@FreeBSD.ORG, bde@FreeBSD.ORG
In-reply-to: <19970822053737.64659@hydrogen.nike.efn.org> (message from John-Mark Gurney on Fri, 22 Aug 1997 05:37:37 -0700)
Subject: Re: does buildworld really use old libs??
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * well.. I was watching buildworld build.. and I noticed something:
 * cc -nostdinc -O2 -pipe   -I/usr/obj/a/home/johng/FreeBSD-checkout/current/src/tm
 * p/usr/include  -o rain rain.o  -ltermcap -lcompat
 * 
 * acording to this line, we are still using the old libraries... shouldn't

Have you tried to move /usr/lib/libtermcap.* out of the way and see if 
it works? :)

 * we add -nostdlib -L${.OBJDIR}/tmp/usr/lib or something similar so that
 * we actually link against the libs that are part of the install set??

The library paths (and some others) are handled by environment
variables.  See COMPILER_ENV.

Satoshi