unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Richard Todd <richardt@vzavenue.net>
Cc: guile-devel@gnu.org
Subject: Re: PATCH for guile-readline/Makefile.am
Date: Wed, 14 Jan 2004 19:17:18 -0600	[thread overview]
Message-ID: <4005EA1E.9090900@vzavenue.net> (raw)
In-Reply-To: <87n08q5k65.fsf@zip.com.au>

Kevin Ryde wrote:
> Richard Todd <richardt@vzavenue.net> writes:
> 
>>If you don't like this method and can find a better way, please do so,
> 
> 
> How about
> 
> 	ln -s $(srcdir)/readline.scm ice-9/readline.scm
> 
> $(srcdir) is right for both in-place and separate builds.

Yeah, I tried that, but for an in-tree build, $(srcdir) == ".".  On the 
two systems I tried it on, that command leads to:
   readline.scm -> ./readline.scm  ( a link ot itself!)

That's why I said it's trickier than it sounds! :)


> 
>>+             (cd ice-9 && $(LN_S) ../$<)  \
>>+        else \
>>+             (cd ice-9 && $(LN_S) $<) \
> 
> 
> Alas, $< is not portable in ordinary rules (see the autoconf manual).
> 

Thanks for pointing this out.  I'll remember that.

For what it's worth, I liked merging readline into guile-core the best, 
but if the license issue is too much to overcome, then I don't see much 
difference in quality between the 'link' approaches and the 'new 
directory' approach.  If there were going to be lots more ice-9/xx.scm 
files for readline, then the new directory would definitlely by cleaner.

thanks,
Richard




_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-01-15  1:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 21:56 PATCH for guile-readline/Makefile.am Richard Todd
2004-01-10 19:41 ` Kevin Ryde
2004-01-10 20:57   ` Marius Vollmer
2004-01-10 23:48 ` Marius Vollmer
2004-01-13 17:38   ` Rob Browning
2004-01-14  0:51     ` Marius Vollmer
2004-01-14  7:41       ` Rob Browning
2004-01-19 18:13       ` Rob Browning
2004-01-19 22:29         ` Kevin Ryde
2004-01-20  6:23           ` Rob Browning
2004-01-20  6:49             ` Rob Browning
2004-01-21 21:31               ` Kevin Ryde
2004-01-14 20:50 ` Kevin Ryde
2004-01-15  1:17   ` Richard Todd [this message]
2004-01-16  6:42     ` Rob Browning

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=4005EA1E.9090900@vzavenue.net \
    --to=richardt@vzavenue.net \
    --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).