Re: Windows paths not considered abolsute in -rpath

[Ralf Wildenhues]

Hello Brendon,

Thanks for the report.

* Brendon Costa wrote on Wed, Dec 13, 2006 at 05:03:03AM CET:
>
[...]
> I am using libtool: 1.5.18
> On system: NetBSD 3.0 i386
[...]
> /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

(Side note: I do hope your cross-compiler is named something like
i386-mingw32-g++ rather than plain g++.)

> libtool: link: only absolute run-paths are allowed

I was going to say "bug" except for...

> DESTDIR=/home/bcosta/i386-mingw32 --host=i386-mingw32

...this which won't work: 'make install' will try to put things below
  ${DESTDIR}${prefix}

but that is
  /home/bcosta/i386-mingw32C:\msys\1.0\blah/lib

so this is a problem.  Forward slashes are portable but fix only half of
the problem here, using /c is not portable to native w32 applications.

Since one cannot expect on NetBSD to have a w32 path rewriting tool, I
don't see any reasonable way to rewrite the above.  And if we rewrite it
in some way, then we must be able to detect the prefixing in the install
rule as well.

If somebody has a good idea for this cross-compilation scenario, I'd
like to hear it.

Cheers,
Ralf