From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: What to do about config.h, etc...
Date: Tue, 11 Mar 2003 21:12:33 -0600 [thread overview]
Message-ID: <87r89d8ehq.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <873cltze3p.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 12 Mar 2003 09:18:50 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> $prefix is pesky, the gnu rule is to expand it at "make" time, not
> configure time, if I understand it correctly.
>
> Nosing around libguile/Makefile.am, I wonder if @prefix@ in the
> libpath.h setup should be $(prefix). Perhaps the other @foo@'s
> similarly (though they're substituted to ${prefix}/something, so end
> up obeying a make-time prefix at least).
Hmm I'll check on that.
> Mind you personally I think anyone who configures with one prefix and
> makes with another is probably asking for trouble, in general.
Well the main thing we need is the ability to install to a prefix
different from that used at configure time. This is required by some
of the packaging systems.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-03-12 3:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 19:04 What to do about config.h, etc Rob Browning
2003-03-04 19:05 ` Andreas Rottmann
2003-03-04 19:53 ` Rob Browning
2003-03-05 0:55 ` Rob Browning
2003-03-13 19:45 ` Rob Browning
2003-03-14 23:16 ` Kevin Ryde
2003-03-14 23:28 ` Kevin Ryde
2003-03-05 14:18 ` Marius Vollmer
2003-03-06 22:04 ` Kevin Ryde
2003-03-07 5:25 ` Rob Browning
2003-03-11 23:18 ` Kevin Ryde
2003-03-12 3:12 ` Rob Browning [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r89d8ehq.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).