From owner-freebsd-questions  Fri Nov 10 16:52:09 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id QAA20775
          for questions-outgoing; Fri, 10 Nov 1995 16:52:09 -0800
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA20757
          for <freebsd-questions@freebsd.org>; Fri, 10 Nov 1995 16:52:01 -0800
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA03579; Fri, 10 Nov 1995 17:54:00 -0700
Date: Fri, 10 Nov 1995 17:54:00 -0700
From: Nate Williams <nate@rocky.sri.MT.net>
Message-Id: <199511110054.RAA03579@rocky.sri.MT.net>
To: Chuck Robey <chuckr@glue.umd.edu>
Cc: Nate Williams <nate@rocky.sri.MT.net>, Archie Cobbs <archie@tribe.com>,
        freebsd-questions@freebsd.org
Subject: Re: ld default path
In-Reply-To: <Pine.SUN.3.91.951110193953.10827B-100000@espresso.eng.umd.edu>
References: <199511110007.RAA03383@rocky.sri.MT.net>
	<Pine.SUN.3.91.951110193953.10827B-100000@espresso.eng.umd.edu>
Sender: owner-questions@freebsd.org
Precedence: bulk

> > > The default search path for "ld" in 2.1-951104-SNAP does not include
> > > /usr/local/lib... should this perhaps be added?
> 
> He's talking about static linking, I was surprised, he's probably right.

Ahh, that's because /usr/local/lib doesn't necessarily exist on all
systems.  Adding very system specific features put you down the long
path to making software *ONLY* work with FreeBSD.  I'd rather keep the
development tools fairly stock.

For an example of what happens when a system does things non-standard,
try porting any Linux-specific software to *anything* else.  Most of the
time it has very Linux-specific paths compiled in, uses Linux-specific
Makefiles, and in general is not portable software.  Portable software
doesn't make any assumptions about anything except for /usr/lib/libc.a.


Nate