You're probably right. The "d:\MonoInstall" was initially entered as "D:/MonoInstall" (forward slashes needed by cygwin). It must have then been mangled by something else making the path invalid when it was used again. Internally d:/ is mapped to /cygdrive/d/ by cygwin, so i assumed it was safe to use that. Looks like it wasn't.
I successfully compiled last night by creating a new directory /svn/mono and doing all my compiling in that. I followed the guide on http://i-nz.net/2006/03/14/compile-mono-svn-head-on-windows/
as written by i-nZ on the mono channel and i finally got it to compile.
Thanks for the help,
Alan.
On 8/1/06, Wade Berrier <[EMAIL PROTECTED]> wrote:
Looks like the rpath may be the issue.
Where does D:\MONOINSTALL/lib come from?
Wade
On Mon, 2006-07-31 at 22:23 +0100, Alan McGovern wrote:
> -rpath D:\MONOINSTALL/lib -no-undefined -version-info 1:0:0
> -Wl,-version-script=
> ./ldscript mini.lo jit-icalls.lo trace.lo dominators.lo cfold.lo
> regalloc.lo hel
> pers.lo liveness.lo ssa.lo abcremoval.lo ssapre.lo aliasing.lo
> local-propagation
> .lo driver.lo debug-mini.lo linear-scan.lo aot-compiler.lo
> aot-runtime.lo graph.
> lo mini-exceptions.lo declsec.lo wapihandles.lo branch-opts.lo
> mini-x86.lo excep
> tions-x86.lo tramp-x86.lo mini-codegen.lo mini-trampolines.lo
> inssel.lo ../../m
> ono/metadata/libmonoruntime.la ../../mono/io-layer/libwapi.la ../../mono/utils/l
> ibmonoutils.la -lgmodule-2.0 -lglib-2.0 -lintl -liconv -lgthread-2.0
> -lglib-2.
> 0 -lintl -liconv ../../libgc/libmonogc.la -lws2_32 -lpsapi -lole32
> -loleaut32
> libtool: link: only absolute run-paths are allowed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQBEzqQQm0+ZqW+3pQwRAjlIAJ9BqdncIQoIkIADYDTXcMjJ2IbGzwCgpyOI
F5dBB4CsYMHNbXjZmXVVrUE=
=l4Dy
-----END PGP SIGNATURE-----
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
