[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ 100058 ] 1.4 - $buildir-path may not contain "~"

From: Gary V . Vaughan
Subject: Re: [ 100058 ] 1.4 - $buildir-path may not contain "~"
Date: Sun, 17 Jun 2001 16:07:40 +0100

On Sunday 17 June 2001  7:50 am, Pavel Roskin wrote:
> Hello, Bruce!
> > > In the mean while, I think the only workaround is to not use '~' in
> > > pathnames.
> Let's not hide the problems. Libtool it misusing IFS. Several macros in
> libtool.m4 set IFS to whatever they want and then run a loop including
> Autoconf macros assuming that the later can work with and IFS.
> I'm sorry to disappoint you. Autoconf provides protection to the configure
> script as a whole, but there is no protection for every single macro
> against the code setting IFS in aclocal.m4 and

Cool.  Thanks for the heads up, I hadn't appreciated that ideom until you 
pointed it out.  However, this doesn't help with splitting a multi-command 
bearing variable on `~' for evaluation, when some of the embedded file paths 
include the field separator character.

> By the way, _LT_AC_TAGCONFIG doesn't restore IFS at all! This causes
> errors with Autoconf 2.50 that uses ":" instead of true. If ":" is in IFS,
> it doesn't work.

I'm partway through a merge of MLB into HEAD.  That macro is just a 

> Autoconf restores IFS inside the loop. Maybe it's not good for speed, but
> it's good for reliability. already uses this trick.

I'll apply this consistently after the merge and before the next alpha 

  ())_.  Gary V. Vaughan     gary@(|
  ( '/   Research Scientist        ,_())____
  / )=   GNU Hacker   \'      `&
`(_~)_   Tech' Author    =`---d__/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]