mainGNU Libtool - Support: sr #100058, 1.4 - $buildir-path may not...

 
 

sr #100058: 1.4 - $buildir-path may not contain "~"

Submitter:  Guido Draheim <guidod>
Submitted:  Thu 14 Jun 2001 06:10:16 AM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  2 - Minor Status:  Done
Privacy:  Public Assigned to:  pogma
Open/Closed:  Closed Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 24 Nov 2004 03:14:09 PM UTC, comment #3: 

And to keep Gary happy :)

I fixed this particular bug with:
<http://savannah.gnu.org/cgi-bin/viewcvs/libtool/libtool/Attic/ltmain.in.diff?r1=1.357&r2=1.358&search=None&hideattic=1>
It was later cleaned up a little and backported to branch-1-5 for Scott's 1.5.2 release.

Peter O'Gorman <pogma>
Group Member
Wed 24 Nov 2004 01:42:50 PM UTC, comment #2: 

I am pretty sure that this is fixed in libtool-1.5.2 and later.

Closing.

Peter O'Gorman <pogma>
Group Member
Sat 16 Jun 2001 05:15:10 PM UTC, comment #1: 


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...

Guido Draheim <guidod>
Thu 14 Jun 2001 06:10:16 AM UTC, original submission:  


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?


Guido Draheim <guidod>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2004-11-24 pogma StatusNone Done
    Assigned toNone pogma
    Open/ClosedOpen Closed

Back to the top

Powered by Savane 3.13-02a9.
Corresponding source code