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 an
"Gary V. Vaughan" wrote:
> ... you have to bear in mind that the libtool source code goes
> through m4, sed and bourne shell, as well as having an autoconf pass to
> subsitute configure time vars, so the quoting is hairy and sensitive to
> change. Meta characters to sed, m4, autoconf or any shel
> Perhaps the problem will go away when we have a binary ltmain in a couple of
> releases?
>
> In the mean while, I think the only workaround is to not use '~' in pathnames.
*sigh* ... actually, I just wonder why it did
work in 1.3.x and it must be left as is in 1.4 - well,
then again,
Support Request #100058, was updated on 2001-Jun-13 23:10
You can respond by visiting:
http://savannah.gnu.org/support/?func=detailsupport&support_id=100058&group_id=25
Category: None
Status: Open
Priority: 5
Summary: 1.4 - $buildir-path may not contain "~"
By: guidod
Date: 2001-Jun-16 10:15
M
Your analysis is correct. Unfortunately, libtool needs to execute multi-line
commands which may contain for loops or if statements, and so setting IFS to
';' breaks. Conceivably we could teach libtool more about parsing shell
code, but it is already far too slow for that to be a practical sol
On Friday 15 June 2001 6:00 pm, Robert Boehne wrote:
> Erik Lindahl wrote:
> > Hi people,
> >
> > We are libtoolizing our fairly large scientific software package.
> >
> > Since fortran is still significantly faster than c on most architectures
> > we use f77 for the innerloops and link it with c
