POSIX paths in #include directives don't work with MinGW

[LRN]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24.03.2013 23:10, Torbjorn Granlund wrote:
> LRN <lrn1986 at gmail.com> writes:
> 
> GMP version: 5.1.1 tarball
> 
> How to reproduce: run ./configure in MSYS on W32, using any
> W32-native MinGW toolchain (doesn't matter which one)
> 
> What is wrong: GMP_INCLUDE_GMP_H and GMP_FUNC_ALLOCA generate
> things like #include "$srcdir/gmp-impl.h" $srcdir is expanded to
> something like "/tc/gmp-5.1.1-1/gmp-5.1.1/gmp-h.in", because the
> shell is POSIXly. However, the compiler (MinGW) is a native W32
> program, and does not understand POSIX paths, fails to compile
> mp_limb_t test, and configure script fails as a result.
> 
> This is a surprising bug report, given that GMP for MingW is in 
> widespread use.  I cannot tell why your install is different.
> 
I can.

The difference is that i'm calling configure script by its absolute
name, i.e. /tc/gmp-5.1.1-1/gmp-5.1.1/configure ...

I've changed absolute name to a relative one (luckily, i know where my
build directory is located in relation to the source directory), and
the problem was gone.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRT1CpAAoJEOs4Jb6SI2CwLDMH/iFqYePRiaV8W3V0qhuKJYET
1ta/3fZUj9o5ocoqjhUR4eBBJGuXaWcwfpRIgNuRRqh5Klww5Ubkib6B4cvHEipu
3eFbS7747yyKtKaCiZ4/QnzwWlw7oWoNf9JKTQCdfJHgrwQiyoiuIgvo+H3K31lc
7cbJigSVNzoQxsufk6mFZVqHw9Uh+OyjlcBSpXLBAujKbwvln5S8tVhuaxDz41R5
BPoO7ooMuw+ZuTaYjP4kDvWSXYD9B0/HqPJVcT5msTrsBjM0XaQqXS3632aUT9FO
ISXkUs2YFPoH5qS/smbhuQZLBK0N45YDr1cT5bBqBxH5SiK5P1SRI/cNQ/i0spI=
=VgT7
-----END PGP SIGNATURE-----