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-13 23:10
Message:
Logged In: YES
user_id=614
Browser: Mozilla/4.7 [en] (X11; U; SunOS 5.6 sun4u)
With the change from 1.3.5 to 1.4
all project builds broke. It boiled
down to the project-path to have a
"~" somewhere in the middle, i.e.
some/project~0.1.3/dir which is
perfectly legal, but at some point
during mode=linking, the libtool
script will barf at "0.1.3/dir"
being nonexistent - it probably
has to do with libtool storing some
command-sequences using a IFS="~"
(delimiter instead of a IFS=";").
Note that the project-path is not
my choice but the one of the local
source-repository system, and that
it does not help to use symlinks to
circumvent the problem - libtool
seems to resolve names for relative
paths to the real-path, i.e. sth.
like -L.. will contain a "~" later.
Since earlier versions had allowed
the buildpath to contain "~", it is
probably possible to fix this issue,
but what to do before that? Is there
a way to get around the problem now?
----------------------------------------------------------------------
You can respond by visiting:
http://savannah.gnu.org/support/?func=detailsupport&support_id=100058&group_id=25
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
