tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Thomas Klausner <wiz@NetBSD.org>
Cc: tech@mdocml.bsd.lv, Alexis <surryhill@gmail.com>
Subject: Re: Allow configure variables to be set from environment
Date: Sat, 17 Jan 2015 02:31:00 +0100	[thread overview]
Message-ID: <20150117013100.GI9772@iris.usta.de> (raw)
In-Reply-To: <20150116233204.GA3640@danbala.tuwien.ac.at>

Hi Thomas,

Thomas Klausner wrote on Sat, Jan 17, 2015 at 12:32:04AM +0100:
> On Fri, Jan 16, 2015 at 10:58:40PM +0100, Alexis wrote:

>> If there is another way to achieve this please let me know.

> Just set them on the 'make' command line, i.e.
> make BINDIR=${BINDIR} PREFIX=${PREFIX} ...

That is fragile at best.  With respect to *DIR, that might work
for now, because ./configure doesn't use the *DIR variables for
anything but to write them into Makefile.local.  But that is an
accident, in principle, ./configure might use them for something
else, too, so putting them into ./configure.local is certainly
more robust.

With respect to PREFIX, your advice doesn't even work.
Try

  make -n PREFIX=FOO install

and it says

  install -m 0555 mandoc demandoc /usr/local/bin

Oops.

That's because the main Makefile does not use PREFIX.
It relies on ./configure to assemble *DIR from PREFIX.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2015-01-17  1:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sfid-H20150116-225859-+021.89-1@spamfilter.osbf.lua>
2015-01-16 21:58 ` Alexis
2015-01-16 23:32   ` Thomas Klausner
2015-01-17  1:31     ` Ingo Schwarze [this message]
2015-01-17  1:07   ` Ingo Schwarze
2015-01-17 20:10     ` Kristaps Dzonsons
2015-01-18  3:33       ` Ingo Schwarze
2015-01-20 15:15         ` Alexis
2015-01-21 23:05           ` Ingo Schwarze
2015-01-22  0:21             ` Kristaps Dzonsons
2015-01-22  0:35               ` Ingo Schwarze
2015-01-22  7:32                 ` Alexis
2015-01-22  7:26             ` Alexis
2015-01-23 22:05               ` Ingo Schwarze
2015-01-20 15:19     ` Alexis
2015-01-21 21:07       ` Ingo Schwarze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150117013100.GI9772@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=surryhill@gmail.com \
    --cc=tech@mdocml.bsd.lv \
    --cc=wiz@NetBSD.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).