Date: Wed, 28 Aug 1996 13:43:56 -0700 From: Scott Blachowicz <scott@statsci.com> To: Ernest Hua <hua@chromatic.com> Cc: Chuck Robey <chuckr@glue.umd.edu>, kientzle@netcom.com, freebsd-ports@freebsd.org Subject: Re: Linux async vs. FreeBSD sync (fwd) Message-ID: <m0uvrSv-000JShC@main.statsci.com> In-Reply-To: Your message of "Wed, 28 Aug 1996 13:00:36 -0700." <199608282000.NAA05510@server1.chromatic.com> References: <199608282000.NAA05510@server1.chromatic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ernest Hua <hua@chromatic.com> wrote:
> Nope. It will just be /usr/local/bin because, like the original
> suggestion, I also symbolic link everything into /usr/local/bin (as well
> as /usr/local/include, /usr/local/lib, /usr/local/lib/app-defaults, ...).
But, if the PREFIX is actually compiled in, you might not have to symlink the
rest of those directories (the actual binaries should have the explicit path
to them). For example, I typically build GNU emacs like this:
cd emacs-19.33
mkdir FREEBSD210
cd FREEBSD210
../configure --prefix=/sw/local/gnu --exec-prefix=/sw/.mtype/gnu
GNU make
[note: /sw/.mtype is amd-redirected to a platform-specific directory]
then I can basically do this:
cd /usr/local/bin
ln -s /sw/local/gnu/bin/* . # or whatever
which isn't really that bad to maintain if the software's installation
directory structure is reasonably organized.
Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div)
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0uvrSv-000JShC>