Date: Fri, 10 Nov 1995 17:54:00 -0700 From: Nate Williams <nate@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 Message-ID: <199511110054.RAA03579@rocky.sri.MT.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511110054.RAA03579>