From: Steinar Bang <sb@metis.no>
Subject: Re: Dave Love's --prefix patch
Date: 14 Aug 1998 11:03:33 +0200 [thread overview]
Message-ID: <whhfzgc4uy.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Steinar Bang's message of "14 Aug 1998 10:43:51 +0200"
>>>>> Steinar Bang <sb@metis.no>:
> [1 <text/plain; US-ASCII (7bit)>]
> Here's Dave Love's patch to Makefile.in to make the install target
> work with the --prefix argument to configure.
> Eg.
> ./configure --prefix=~/apps
Er... when I look at it, this patch looks a bit,
umm... superflous... maybe I should have tried installing 5.6.34
before applying the patches...?
> [2 love-prefix.patch <application/octet-stream>]
> *** Makefile.in.distrib Fri Aug 14 10:32:54 1998
> --- Makefile.in Fri Aug 14 10:34:25 1998
> ***************
> *** 1,5 ****
> --- 1,7 ----
> prefix = @prefix@
> datadir = @datadir@
> + prefix = @prefix@
> + datadir = @datadir@
> lispdir = @lispdir@
> srcdir = @srcdir@
prev parent reply other threads:[~1998-08-14 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-14 8:43 Steinar Bang
1998-08-14 9:03 ` Steinar Bang [this message]
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=whhfzgc4uy.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).