unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: Tom Willemsen <tom@ryuslash.org>
Cc: guile-user@gnu.org
Subject: Re: Multiple version
Date: Mon, 02 Apr 2012 20:32:39 -0400	[thread overview]
Message-ID: <rmibon964ew.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <m3ehs58yaz.fsf@ryuslash.org> (Tom Willemsen's message of "Tue, 03 Apr 2012 02:16:20 +0200")

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]


  I was wondering if it's possible to have guile 1.8 and guile 2.0
  installed on the same system? I remember reading in the documentation
  that it is, but I haven't been able to pull it off yet, except by using
  different --prefix values for each.

pkgsrc (a packaging system originally for NetBSD, but also supports
other BSDs, Linux, *Solaris, and others) doesn't have guile 2 yet (my
fault :-) but has 1.6 and 1.8.  1.8 is installed normally
(--prefix=/usr/pkg, named guile) and guile1.6 is installed
--prefix=/usr/pkg/guile/1.6.   So that's a data point about others'
approach to your problem.

  I don't know enough about the autotools to know what to do with
  guile.m4. Does automake/autoconf expect the file name to match
  something, or does it only look at the definitions inside, in which case
  it could simply be moved.

You only need that to run autoconf on programs that depend on guile, and
either should be ok.  So you could patch it out of the 2.0 build.
But having a separate prefix seems easiest.

What's wrong (or actually problematic) about using /usr/guile2 as the
prefix for guile 2.0, and putting it in your path and/or passing that
for building other things?

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2012-04-03  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  0:16 Multiple version Tom Willemsen
2012-04-03  0:32 ` Greg Troxel [this message]
2012-04-03  7:48   ` Tom Willemsen
2012-04-03 16:47     ` Greg Troxel

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=rmibon964ew.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=guile-user@gnu.org \
    --cc=tom@ryuslash.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).