[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Windows paths not considered abolsute in -rpath
From: |
Brendon Costa |
Subject: |
Windows paths not considered abolsute in -rpath |
Date: |
Wed, 13 Dec 2006 15:03:03 +1100 |
User-agent: |
Mozilla Thunderbird 1.0.7 (X11/20051204) |
Hi,
I am not entirely sure if this is the correct behaviour for libtool or
not, but if i compile a program that supports cross compiling using
libtool like:
/path/to/configure --prefix=C:\\msys\\1.0\\blah
DESTDIR=/home/bcosta/i386-mingw32 --host=i386-mingw32
make
it get an error while it is creating the libtool library for the -rpath.
It does not seem to associate the windows native paths C:\ as being an
absolute path (Possibly it just searches for the start of the string for
the / character). Note it does work if i use /c/blah
Is this a bug or a feature?
I am using libtool: 1.5.18
On system: NetBSD 3.0 i386
The appropiate line which produces the error looks a little like:
/usr/pkg/bin/bash ../../libtool --tag=CXX --mode=link g++ -g -O2 -o
libADS_System.la -rpath C:\msys\1.0\blah/lib -no-undefined
-Wl,--enable-runtime-pseudo-reloc libADS_System_la-ADS_System.lo ...
more objects
libtool: link: only absolute run-paths are allowed
Thanks,
Brendon.
- Windows paths not considered abolsute in -rpath,
Brendon Costa <=