Groups > comp.os.linux.development.apps > #783

Re: How do I configure Autotools files for libexec installs?

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!fx28.iad.POSTED!not-for-mail
From	Lew Pitcher <lew.pitcher@digitalfreehold.ca>
Subject	Re: How do I configure Autotools files for libexec installs?
Newsgroups	comp.os.linux.development.apps
References	<RZGax.14329$FK.8477@fx13.iad> <wwvzj4khddw.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid>
Lines	40
Organization	The Pitcher Digital Freehold
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Content-Transfer-Encoding	7Bit
X-ClacksOverhead	RIP Dennis M Richie
Message-ID	<PAHax.75232$jB1.5220@fx28.iad> (permalink)
X-Complaints-To	abuse@UsenetServer.com
NNTP-Posting-Date	Sun, 31 May 2015 17:32:31 UTC
Date	Sun, 31 May 2015 13:32:30 -0400
X-Received-Bytes	1960
X-Received-Body-CRC	3588420169
Xref	csiph.com comp.os.linux.development.apps:783

Show key headers only | View raw

On Sunday May 31 2015 13:20, in comp.os.linux.development.apps, "Richard
Kettlewell" <rjk@greenend.org.uk> wrote:

> Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
> [...]
>> but none have resulted in a Makefile that would actually install the
>> file into the intended directory. Usually the @libexec@ just expands
>> into a literal '${exec_prefix}/libexec' path, without expanding the
>> ${exec_prefix}.  Even the explicit '${exec_prefix}/libexec' just
>> "expands" into '${prefix}/libexec', still leaving the path unusable.
> 
> You need definitions for exec_prefix and prefix as well.  Example:
> 
>   $ cat configure.ac
>   AC_INIT([whatever], [0.0], [whatever@example.com])
>   AC_CONFIG_FILES([Makefile])
>   AC_OUTPUT
>   $ cat Makefile.in
>   prefix=@prefix@
>   exec_prefix=@exec_prefix@
>   libbexecdir=@libexecdir@
>   $ autoconf
>   $ ./configure
>   configure: creating ./config.status
>   config.status: creating Makefile
>   $ cat Makefile
>   prefix=/usr/local
>   exec_prefix=${prefix}
>   libbexecdir=${exec_prefix}/libexec

That's what I needed to see.

Thank you. I'll give it a try.


-- 
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request

Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 12:50 -0400
  Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 12:55 -0400
    Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:12 -0400
  Re: How do I configure Autotools files for libexec installs? Richard Kettlewell <rjk@greenend.org.uk> - 2015-05-31 18:20 +0100
    Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:31 -0400
    Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:32 -0400
    Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:56 -0400

csiph-web