This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: /usr/local/libexec support
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Geoffrey Keating <gkeating at apple dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 30 Jul 2003 17:06:26 -0400
- Subject: Re: /usr/local/libexec support
- References: <200307300700.h6U70hnP002315@keatge.apple.com>
On Wed, Jul 30, 2003 at 12:00:43AM -0700, Geoffrey Keating wrote:
>
> This patch implements support in GCC for the 'libexecdir' variable and
> configure option, following this part of the GNU Makefile standard:
>
> `libdir'
> The directory for object files and libraries of object code. Do
> not install executables here, they probably ought to go in
> `$(libexecdir)' instead.
>
> `libexecdir'
> The directory for installing executable programs to be run by other
> programs rather than by users. This directory should normally be
> `/usr/local/libexec', but write it as `$(exec_prefix)/libexec'.
>
> GCC now places executables in
> $prefix/libexec/gcc/<target>/<version>/{cc1,cc1plus,...}
> Data files (include files, etc.) are still placed in
> $prefix/lib/gcc-lib/<target>/<version>/...
>
> I would be interested in opinions as to whether we should rename the
> redundant "gcc-lib" to "gcc" at this point.
Either way, I think the two directory names should be consistent. At
which point, please make sure that everything works if they're the same
directory...
Most GNU/Linux systems configure using --libexecdir=$(libdir). Don't
ask me why.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer