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

[nobody]

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

Message:
Logged In: YES 
user_id=614
Browser: Mozilla/4.76 [de] (X11; U; Linux 2.2.17 i586)

Gary V.Vaughan wrote:
> 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 don't know why it did
work in 1.3.x and it must be left as is in 1.4 - well,
then again, libtool gained functionality...

btw, after a bit of trial-and-error, I am using now
a builddir outside the source-archive where the
original files are symlinked. That way any updates
to the files through the archive (from co-developments)
are directly reflected in the builddir, and all the
real-paths of directories do not contain a "~".

Hopefully, the "~" can be solved later on...


----------------------------------------------------------------------

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