msys2-users

[Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

I'm trying to build monotone using MinGW64. monotone is written in C++,
so it requires the g++ compiler.

In msys2, 'pacman -Ss g++' returns no results, so it appears g++ has not
yet been packaged for msys2; is this correct?

The other option is to use MinGW64, which does provide g++.

However, the MinGW64 compiler does not support Msys2 symlinks. Several
of the packages required by monotone use symlinks (when supported) in
the build process. 'configure' recognizes that msys2 supports symlinks,
and it assumes that 'gcc' does as well.

The dependent packages don't need g++, so I could compile them with
msys2 gcc. However, I'm worried about compatibility of the two runtimes.
MinGW64 offers several options for the runtime; which ones were used for
the msys2 version?

My current workaround is to run configure in msys2, which defines "LN_S = ln -s"
in the generated Makefile, then edit that to "LN_S = cp -pR", then
compile with MinGW64 gcc.

Is there a better way?

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Ray D. <min...@gm...>]

Hi Stephe,

pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain [remove
any arch you don't care about]

It may good to read the following ticket where I walk people through
setting up a dev. env and building python2 from source (using our
PKGBUILD recipe - I recommend making a PKGBUILD for monotone and
submitting it to us too if you have the time/inclination!):

http://sourceforge.net/p/msys2/tickets/32/?limit=10&page=1#216b

Cheers,

Ray.


On Tue, Apr 29, 2014 at 10:32 AM, Stephen Leake
<ste...@st...> wrote:
> I'm trying to build monotone using MinGW64. monotone is written in C++,
> so it requires the g++ compiler.
>
> In msys2, 'pacman -Ss g++' returns no results, so it appears g++ has not
> yet been packaged for msys2; is this correct?
>
> The other option is to use MinGW64, which does provide g++.
>
> However, the MinGW64 compiler does not support Msys2 symlinks. Several
> of the packages required by monotone use symlinks (when supported) in
> the build process. 'configure' recognizes that msys2 supports symlinks,
> and it assumes that 'gcc' does as well.
>
> The dependent packages don't need g++, so I could compile them with
> msys2 gcc. However, I'm worried about compatibility of the two runtimes.
> MinGW64 offers several options for the runtime; which ones were used for
> the msys2 version?
>
> My current workaround is to run configure in msys2, which defines "LN_S = ln -s"
> in the generated Makefile, then edit that to "LN_S = cp -pR", then
> compile with MinGW64 gcc.
>
> Is there a better way?
>
> --
> -- Stephe
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Ray Donnelly <min...@gm...> writes:

> Hi Stephe,
>
> pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain [remove
> any arch you don't care about]
>
> It may good to read the following ticket where I walk people through
> setting up a dev. env and building python2 from source (using our
> PKGBUILD recipe - I recommend making a PKGBUILD for monotone and
> submitting it to us too if you have the time/inclination!):
>
> http://sourceforge.net/p/msys2/tickets/32/?limit=10&page=1#216b

That helps, thanks.

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Stephen Leake <ste...@st...> writes:

> Ray Donnelly <min...@gm...> writes:
>
>> pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain 
>
> That helps, thanks.

I take it back :)

configure is trying to find the Botan I installed, but g++ doesn't
seem understand the filesystem:

$ mount
C:/Msys2/msys64 on /usr type ntfs (binary,noacl,auto)
C:/Msys2/msys64 on / type ntfs (binary,noacl,auto)
C: on /c type ntfs (binary,noacl,posix=0,user,noumount,auto)
$ type g++
g++ is hashed (/Msys2/msys64/mingw64/bin/g++) 
$ g++ -v -o conftest0 -I/mingw64/include -g -O2 -Wall  -I/mingw64/include/botan-1.10 -L/mingw64/lib conftest.cpp -lz  -lbotan-1.10 
Using built-in specs.
COLLECT_GCC=C:\Msys2\msys64\mingw64\bin\g++.exe
COLLECT_LTO_WRAPPER=C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../gcc-4.9.0/configure --prefix=/mingw64 --with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include --libexecdir=/mingw64/lib --with-gxx-include-dir=/mingw64/include/c++/4.9.0 --enable-bootstrap --with-arch=x86-64 --with-tune=generic --enable-languages=c,lto,c++,objc,obj-c++,fortran,ada --enable-shared --enable-static --enable-libatomic --enable-threads=posix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-time=yes --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-cloog-backend=isl --enable-version-specific-runtime-libs --disable-cloog-version-check --disable-isl-version-check --enable-lto --enable-libgomp --disable-multilib --enable-checking=release --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64 --with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64 --with-cloog=/mingw64 --with-pkgversion='Rev1, Built by MSYS2 project' --with-bugurl=http://sourceforge.net/projects/msys2 --with-gnu-as --with-gnu-ld
Thread model: posix
gcc version 4.9.0 (Rev1, Built by MSYS2 project) 
COLLECT_GCC_OPTIONS='-v' '-o' 'conftest0.exe' '-I' '/mingw64/include' '-g' '-O2' '-Wall' '-I' '/mingw64/include/botan-1.10' '-L/mingw64/lib' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
 C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/cc1plus.exe -quiet -v -I /mingw64/include -I /mingw64/include/botan-1.10 -iprefix C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/ -D_REENTRANT conftest.cpp -quiet -dumpbase conftest.cpp -mtune=generic -march=x86-64 -auxbase conftest -g -O2 -Wall -version -o C:\tmp\cc1z4ika.s
GNU C++ (Rev1, Built by MSYS2 project) version 4.9.0 (x86_64-w64-mingw32)
	compiled by GNU C version 4.9.0, GMP version 6.0.0, MPFR version 3.1.2-p5, MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
ignoring duplicate directory "C:/Msys2/msys64/mingw64/lib/gcc/../../lib/gcc/x86_64-w64-mingw32/4.9.0/include"
ignoring nonexistent directory "C:/msys64/mingw64/include"
ignoring nonexistent directory "/mingw64/include"
ignoring duplicate directory "C:/Msys2/msys64/mingw64/lib/gcc/../../lib/gcc/x86_64-w64-mingw32/4.9.0/include-fixed"
ignoring duplicate directory "C:/Msys2/msys64/mingw64/lib/gcc/../../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/include"
ignoring nonexistent directory "C:/msys64/mingw64/x86_64-w64-mingw32/include"
ignoring nonexistent directory "/mingw64/include"
ignoring nonexistent directory "/mingw64/include/botan-1.10"
#include "..." search starts here:
#include <...> search starts here:
 C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/include
 C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../include
 C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/include-fixed
 C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/include
 C:/Msys2/msys64/mingw64/lib/gcc/../../include/c++/4.9.0
 C:/Msys2/msys64/mingw64/lib/gcc/../../include/c++/4.9.0/x86_64-w64-mingw32
 C:/Msys2/msys64/mingw64/lib/gcc/../../include/c++/4.9.0/backward
End of search list.
GNU C++ (Rev1, Built by MSYS2 project) version 4.9.0 (x86_64-w64-mingw32)
	compiled by GNU C version 4.9.0, GMP version 6.0.0, MPFR version 3.1.2-p5, MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 24a2abd61b42a3ceb183d4c0b02e83f2
conftest.cpp:14:25: fatal error: botan/botan.h: No such file or directory
 #include <botan/botan.h>
                         ^
compilation terminated.


In particular, note:

ignoring nonexistent directory "C:/msys64/mingw64/include"
ignoring nonexistent directory "/mingw64/include"

This was run in a shell I spawned under Emacs. To see if that causes the
problem, I ran in the msys shell spawned by msys2_shell.bat; that was
worse: 

$ export PATH=/Msys2/msys64/mingw64/bin:$PATH
$ g++ -v -o conftest0 -I/mingw64/include -g -O2 -Wall  -I/mingw64/include/botan-1.10 -L/mingw64/lib conftest.cpp -lz  -lbotan-1.10 g++ -v -o conftest0 -I/mingw64/include -g -O2 -Wall  -I/mingw64/include/botan-1.10 -L/mingw64/lib conftest.cpp -lz  -lbotan-1.10
g++.exe: error: g++: No such file or directory
Using built-in specs.
COLLECT_GCC=C:\Msys2\msys64\mingw64\bin\g++.exe
COLLECT_LTO_WRAPPER=C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../gcc-4.9.0/configure --prefix=/mingw64 --with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include --libexecdir=/mingw64/lib --with-gxx-include-dir=/mingw64/include/c++/4.9.0 --enable-bootstrap --with-arch=x86-64 --with-tune=generic --enable-languages=c,lto,c++,objc,obj-c++,fortran,ada --enable-shared --enable-static --enable-libatomic --enable-threads=posix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-time=yes --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-cloog-backend=isl --enable-version-specific-runtime-libs --disable-cloog-version-check --disable-isl-version-check --enable-lto --enable-libgomp --disable-multilib --enable-checking=release --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64 --with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64 --with-cloog=/mingw64 --with-pkgversion='Rev1, Built by MSYS2 project' --with-bugurl=http://sourceforge.net/projects/msys2 --with-gnu-as --with-gnu-ld
Thread model: posix
gcc version 4.9.0 (Rev1, Built by MSYS2 project)

Note: 'g++.exe: error: g++: No such file or directory', and that there is
no further output.


-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Alexpux <al...@gm...>]

29 апр. 2014 г., в 23:09, Stephen Leake <ste...@st...> написал(а):

> Stephen Leake <ste...@st...> writes:
> 
>> Ray Donnelly <min...@gm...> writes:
>> 
>>> pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain 
>> 
>> That helps, thanks.
> 
> I take it back :)
> 
> configure is trying to find the Botan I installed, but g++ doesn't
> seem understand the filesystem:

First, I’m upload today more rebuilds include GCC-4.9.0-2. Please update system: pacman -Syu
> 
> $ mount
> C:/Msys2/msys64 on /usr type ntfs (binary,noacl,auto)
> C:/Msys2/msys64 on / type ntfs (binary,noacl,auto)
> C: on /c type ntfs (binary,noacl,posix=0,user,noumount,auto)
> $ type g++
> g++ is hashed (/Msys2/msys64/mingw64/bin/g++) 
> $ g++ -v -o conftest0 -I/mingw64/include -g -O2 -Wall  -I/mingw64/include/botan-1.10 -L/mingw64/lib conftest.cpp -lz  -lbotan-1.10 
> Using built-in specs.
> COLLECT_GCC=C:\Msys2\msys64\mingw64\bin\g++.exe
> COLLECT_LTO_WRAPPER=C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/lto-wrapper.exe
> Target: x86_64-w64-mingw32
> Configured with: ../gcc-4.9.0/configure --prefix=/mingw64 --with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include --libexecdir=/mingw64/lib --with-gxx-include-dir=/mingw64/include/c++/4.9.0 --enable-bootstrap --with-arch=x86-64 --with-tune=generic --enable-languages=c,lto,c++,objc,obj-c++,fortran,ada --enable-shared --enable-static --enable-libatomic --enable-threads=posix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-time=yes --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-cloog-backend=isl --enable-version-specific-runtime-libs --disable-cloog-version-check --disable-isl-version-check --enable-lto --enable-libgomp --disable-multilib --enable-checking=release --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64 --with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64 --with-cloog=/mingw64 --with-pkgversion='Rev1, Built by MSYS2 project' --with-bugurl=http://sourceforge.net/projects/msys2 --with-gnu-as --with-gnu-ld
> Thread model: posix
> gcc version 4.9.0 (Rev1, Built by MSYS2 project) 
> COLLECT_GCC_OPTIONS='-v' '-o' 'conftest0.exe' '-I' '/mingw64/include' '-g' '-O2' '-Wall' '-I' '/mingw64/include/botan-1.10' '-L/mingw64/lib' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
> C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/cc1plus.exe -quiet -v -I /mingw64/include -I /mingw64/include/botan-1.10 -iprefix C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/ -D_REENTRANT conftest.cpp -quiet -dumpbase conftest.cpp -mtune=generic -march=x86-64 -auxbase conftest -g -O2 -Wall -version -o C:\tmp\cc1z4ika.s
> GNU C++ (Rev1, Built by MSYS2 project) version 4.9.0 (x86_64-w64-mingw32)
> 	compiled by GNU C version 4.9.0, GMP version 6.0.0, MPFR version 3.1.2-p5, MPC version 1.0.2
> GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> ignoring duplicate directory "C:/Msys2/msys64/mingw64/lib/gcc/../../lib/gcc/x86_64-w64-mingw32/4.9.0/include"
> ignoring nonexistent directory "C:/msys64/mingw64/include"
> ignoring nonexistent directory "/mingw64/include"
> ignoring duplicate directory "C:/Msys2/msys64/mingw64/lib/gcc/../../lib/gcc/x86_64-w64-mingw32/4.9.0/include-fixed"
> ignoring duplicate directory "C:/Msys2/msys64/mingw64/lib/gcc/../../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/include"
> ignoring nonexistent directory "C:/msys64/mingw64/x86_64-w64-mingw32/include"
> ignoring nonexistent directory "/mingw64/include"
> ignoring nonexistent directory "/mingw64/include/botan-1.10"
> #include "..." search starts here:
> #include <...> search starts here:
> C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/include
> C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../include
> C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/include-fixed
> C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/../../../../x86_64-w64-mingw32/include
> C:/Msys2/msys64/mingw64/lib/gcc/../../include/c++/4.9.0
> C:/Msys2/msys64/mingw64/lib/gcc/../../include/c++/4.9.0/x86_64-w64-mingw32
> C:/Msys2/msys64/mingw64/lib/gcc/../../include/c++/4.9.0/backward
> End of search list.
> GNU C++ (Rev1, Built by MSYS2 project) version 4.9.0 (x86_64-w64-mingw32)
> 	compiled by GNU C version 4.9.0, GMP version 6.0.0, MPFR version 3.1.2-p5, MPC version 1.0.2
> GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> Compiler executable checksum: 24a2abd61b42a3ceb183d4c0b02e83f2
> conftest.cpp:14:25: fatal error: botan/botan.h: No such file or directory
> #include <botan/botan.h>
>                         ^
> compilation terminated.
> 
> 
> In particular, note:
> 
> ignoring nonexistent directory "C:/msys64/mingw64/include"
> ignoring nonexistent directory "/mingw64/include"
> 
> This was run in a shell I spawned under Emacs. To see if that causes the
> problem, I ran in the msys shell spawned by msys2_shell.bat; that was
> worse: 
> 
> $ export PATH=/Msys2/msys64/mingw64/bin:$PATH
export PATH=/mingw64/bin:$PATH
See the difference between commands

> $ g++ -v -o conftest0 -I/mingw64/include -g -O2 -Wall  -I/mingw64/include/botan-1.10 -L/mingw64/lib conftest.cpp -lz  -lbotan-1.10 g++ -v -o conftest0 -I/mingw64/include -g -O2 -Wall  -I/mingw64/include/botan-1.10 -L/mingw64/lib conftest.cpp -lz  -lbotan-1.10
> g++.exe: error: g++: No such file or directory
> Using built-in specs.
> COLLECT_GCC=C:\Msys2\msys64\mingw64\bin\g++.exe
> COLLECT_LTO_WRAPPER=C:/Msys2/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.0/lto-wrapper.exe
> Target: x86_64-w64-mingw32
> Configured with: ../gcc-4.9.0/configure --prefix=/mingw64 --with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include --libexecdir=/mingw64/lib --with-gxx-include-dir=/mingw64/include/c++/4.9.0 --enable-bootstrap --with-arch=x86-64 --with-tune=generic --enable-languages=c,lto,c++,objc,obj-c++,fortran,ada --enable-shared --enable-static --enable-libatomic --enable-threads=posix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-time=yes --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-cloog-backend=isl --enable-version-specific-runtime-libs --disable-cloog-version-check --disable-isl-version-check --enable-lto --enable-libgomp --disable-multilib --enable-checking=release --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64 --with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64 --with-cloog=/mingw64 --with-pkgversion='Rev1, Built by MSYS2 project' --with-bugurl=http://sourceforge.net/projects/msys2 --with-gnu-as --with-gnu-ld
> Thread model: posix
> gcc version 4.9.0 (Rev1, Built by MSYS2 project)
> 
> Note: 'g++.exe: error: g++: No such file or directory', and that there is
> no further output.
> 
> 
> -- 
> -- Stephe
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Stephen Leake <ste...@st...> writes:

> Stephen Leake <ste...@st...> writes:
>
>> Ray Donnelly <min...@gm...> writes:
>>
>>> pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain 
>>
>> That helps, thanks.
>
> I take it back :)
>
> configure is trying to find the Botan I installed, but g++ doesn't
> seem understand the filesystem:

I thought the solution might be to use mingw-w64-cross-toolchain, but
that does not install gcc or g++;

$ ls /Msys2/msys64/bin/*gcc*
/Msys2/msys64/bin/msys-gcc_s-seh-1.dll
/Msys2/msys64/bin/msys-gccpp-1.dll
$ ls /Msys2/msys64/bin/*gcc*
/Msys2/msys64/bin/msys-gcc_s-seh-1.dll
/Msys2/msys64/bin/msys-gccpp-1.dll

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Stephen Leake <ste...@st...> writes:

> Stephen Leake <ste...@st...> writes:
>
>> Stephen Leake <ste...@st...> writes:
>>
>>> Ray Donnelly <min...@gm...> writes:
>>>
>>>> pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain 
>>>
>>> That helps, thanks.
>>
>> I take it back :)
>>
>> configure is trying to find the Botan I installed, but g++ doesn't
>> seem understand the filesystem:

I found the solution. mingw64/bin/g++ is not an msys tool, so it doesn't
know msys paths. So use Windows paths!

$ g++ -v -o conftest0 -I/Msys2/msys64/mingw64/include -g -O2 -Wall  -I/Msys2/msys64/mingw64/include/botan-1.10 -L/Msys2/msys64/mingw64/lib conftest.cpp -lz  -lbotan-1.10 

That works.

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Ray D. <min...@gm...>]

msys2 should convert paths depending on the nature of the executable
(msys vs native).

I've got a strong feeling that you should start from scratch so I am
writing a complete run down of getting everything in place to start
working on monotone. Are you interested in me completing this guide?

On Wed, Apr 30, 2014 at 12:15 AM, Stephen Leake
<ste...@st...> wrote:
> Stephen Leake <ste...@st...> writes:
>
>> Stephen Leake <ste...@st...> writes:
>>
>>> Stephen Leake <ste...@st...> writes:
>>>
>>>> Ray Donnelly <min...@gm...> writes:
>>>>
>>>>> pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain
>>>>
>>>> That helps, thanks.
>>>
>>> I take it back :)
>>>
>>> configure is trying to find the Botan I installed, but g++ doesn't
>>> seem understand the filesystem:
>
> I found the solution. mingw64/bin/g++ is not an msys tool, so it doesn't
> know msys paths. So use Windows paths!
>
> $ g++ -v -o conftest0 -I/Msys2/msys64/mingw64/include -g -O2 -Wall  -I/Msys2/msys64/mingw64/include/botan-1.10 -L/Msys2/msys64/mingw64/lib conftest.cpp -lz  -lbotan-1.10
>
> That works.
>
> --
> -- Stephe
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Ray D. <min...@gm...>]

Here's my start from scratch instructions anyway. I got as far as
having trouble with botan, but it's too late in the evening now.

You can of course have multiple MSYS2/MinGW instances on your machine
without conflicts, so long as you don't run two (different) instances
at once (due to DLL rebasing issues).

Your goal is to build monotone for native Windows 64bit? Here's a
rundown of the steps I tried:

Download and unpack msys2-base-x86_64-20140216.tar.xz, I'm going to do
this to E:\monotone and pretend you did the same just to simplify the
instructions.

Since you want to build Win64 software, you should run
E:\monotone\msys64\mingw64_shell.bat
.. It will create the initial environment.
$ exit
run E:\monotone\msys64\mingw64_shell.bat
$ pacman -Syu
it will update the core system causing DLL address conflicts and we
need to rebase the MSYS dlls.
$ exit
wait for bash to go away (can take 20-30 seconds), then run
E:\monotone\msys64\autorebase.bat then run
E:\monotone\msys64\mingw64_shell.bat
.. install base development tools:
$ pacman -S base-devel tar
$ exit
wait for bash to go away again then run
E:\monotone\msys64\autorebase.bat again then run
E:\monotone\msys64\mingw64_shell.bat again. Since we'll not update any
more MSYS DLLs this should be the last time we need to do this.
.. install monotone dependencies which I guess are:
$ pacman -S mingw-w64-x86_64-toolchain mingw64/mingw-w64-x86_64-boost
mingw64/mingw-w64-x86_64-gettext mingw64/mingw-w64-x86_64-libiconv
mingw64/mingw-w64-x86_64-libidn mingw64/mingw-w64-x86_64-lua
mingw64/mingw-w64-x86_64-pcre mingw64/mingw-w64-x86_64-pkgconf
mingw64/mingw-w64-x86_64-sqlite3 mingw64/mingw-w64-x86_64-zlib

.. then we need to build botan. I hoped we had botan already as a
package (I guess you compiled it already?) but it seems not, and my
quick attempt to build it failed:

In file included from build/include/botan/certstor.h:11:0,
                 from src/lib/cert/x509/certstor.cpp:8:
build/include/botan/x509cert.h:228:7: note:
Botan::X509_Certificate::X509_Certificate()
       X509_Certificate() {}
       ^
build/include/botan/x509cert.h:228:7: note:   candidate expects 0
arguments, 1 provided
build/include/botan/x509cert.h:221:7: note:
Botan::X509_Certificate::X509_Certificate(const std::vector<unsigned
char>&)
       X509_Certificate(const std::vector<byte>& in);
       ^

.. if you have any hints on that the please let me know. Of course the
goal for botan (and then monotone) is to make a PKGBUILD recipe, for
example something like
https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-libpng/PKGBUILD

Cheers,

Ray.

On Tue, Apr 29, 2014 at 11:11 PM, Stephen Leake
<ste...@st...> wrote:
> Stephen Leake <ste...@st...> writes:
>
>> Stephen Leake <ste...@st...> writes:
>>
>>> Ray Donnelly <min...@gm...> writes:
>>>
>>>> pacman -S mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain
>>>
>>> That helps, thanks.
>>
>> I take it back :)
>>
>> configure is trying to find the Botan I installed, but g++ doesn't
>> seem understand the filesystem:
>
> I thought the solution might be to use mingw-w64-cross-toolchain, but
> that does not install gcc or g++;
>
> $ ls /Msys2/msys64/bin/*gcc*
> /Msys2/msys64/bin/msys-gcc_s-seh-1.dll
> /Msys2/msys64/bin/msys-gccpp-1.dll
> $ ls /Msys2/msys64/bin/*gcc*
> /Msys2/msys64/bin/msys-gcc_s-seh-1.dll
> /Msys2/msys64/bin/msys-gccpp-1.dll
>
> --
> -- Stephe
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Ray Donnelly <min...@gm...> writes:

> msys2 should convert paths depending on the nature of the executable
> (msys vs native).

do you mean "g++" instead of "msys2"?

> I've got a strong feeling that you should start from scratch 

I just did, twice :)

> so I am writing a complete run down of getting everything in place to
> start working on monotone. Are you interested in me completing this
> guide?

Yes. Attached is what I have so far.

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Stephen Leake <ste...@st...> writes:

> Ray Donnelly <min...@gm...> writes:
>
>> msys2 should convert paths depending on the nature of the executable
>> (msys vs native).
>
> do you mean "g++" instead of "msys2"?

Or is it "the msys2 dll that g++ uses to access the file system" that
does the path conversion?

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Ray Donnelly <min...@gm...> writes:

> Your goal is to build monotone for native Windows 64bit? 

Yes.

> Here's a rundown of the steps I tried:
>
> Download and unpack msys2-base-x86_64-20140216.tar.xz, I'm going to do
> this to E:\monotone and pretend you did the same just to simplify the
> instructions.

I installed to c:\msys2

One possible complication: I have Cygwin installed at c:\, so /bin is
the Cygwin bin.  But that doesn't seem to be a problem so far.

> Since you want to build Win64 software, you should run
> E:\monotone\msys64\mingw64_shell.bat
> .. It will create the initial environment.
> $ exit
> run E:\monotone\msys64\mingw64_shell.bat
> $ pacman -Syu
> it will update the core system causing DLL address conflicts and we
> need to rebase the MSYS dlls.
> $ exit
> wait for bash to go away (can take 20-30 seconds), then run
> E:\monotone\msys64\autorebase.bat then run
> E:\monotone\msys64\mingw64_shell.bat

same as my list so far.

> .. install base development tools:
> $ pacman -S base-devel tar
> $ exit
> wait for bash to go away again then run
> E:\monotone\msys64\autorebase.bat again then run
> E:\monotone\msys64\mingw64_shell.bat again. Since we'll not update any
> more MSYS DLLs this should be the last time we need to do this.
> .. install monotone dependencies which I guess are:
> $ pacman -S mingw-w64-x86_64-toolchain mingw64/mingw-w64-x86_64-boost
> mingw64/mingw-w64-x86_64-gettext mingw64/mingw-w64-x86_64-libiconv
> mingw64/mingw-w64-x86_64-libidn mingw64/mingw-w64-x86_64-lua
> mingw64/mingw-w64-x86_64-pcre mingw64/mingw-w64-x86_64-pkgconf
> mingw64/mingw-w64-x86_64-sqlite3 mingw64/mingw-w64-x86_64-zlib

I installed mingw-w64-x86_64-toolchain, which includes several of the
above.

I could not find out which package actually installs g++; 'pacman -Qo
g++' gives 'error: No package owns /usr/mingw64/bin/g++'. So I don't
know how to minimize the number of packages installed (not critical).

> .. then we need to build botan. I hoped we had botan already as a
> package (I guess you compiled it already?) but it seems not, and my
> quick attempt to build it failed:

I had no problems with botan once I fixed the directory separators in
configure.

I'm currently stuck running configure for monotone; it's giving several
odd errors.

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Alexpux <al...@gm...>]

30 апр. 2014 г., в 5:38, Stephen Leake <ste...@st...> написал(а):

> Ray Donnelly <min...@gm...> writes:
> 
>> Your goal is to build monotone for native Windows 64bit? 
> 
> Yes.
> 
>> Here's a rundown of the steps I tried:
>> 
>> Download and unpack msys2-base-x86_64-20140216.tar.xz, I'm going to do
>> this to E:\monotone and pretend you did the same just to simplify the
>> instructions.
> 
> I installed to c:\msys2
> 
> One possible complication: I have Cygwin installed at c:\, so /bin is
> the Cygwin bin.  But that doesn't seem to be a problem so far.
You need to not have Cygwin bin directory in the PATH.
> 
>> Since you want to build Win64 software, you should run
>> E:\monotone\msys64\mingw64_shell.bat
>> .. It will create the initial environment.
>> $ exit
>> run E:\monotone\msys64\mingw64_shell.bat
>> $ pacman -Syu
>> it will update the core system causing DLL address conflicts and we
>> need to rebase the MSYS dlls.
>> $ exit
>> wait for bash to go away (can take 20-30 seconds), then run
>> E:\monotone\msys64\autorebase.bat then run
>> E:\monotone\msys64\mingw64_shell.bat
> 
> same as my list so far.
> 
>> .. install base development tools:
>> $ pacman -S base-devel tar
>> $ exit
>> wait for bash to go away again then run
>> E:\monotone\msys64\autorebase.bat again then run
>> E:\monotone\msys64\mingw64_shell.bat again. Since we'll not update any
>> more MSYS DLLs this should be the last time we need to do this.
>> .. install monotone dependencies which I guess are:
>> $ pacman -S mingw-w64-x86_64-toolchain mingw64/mingw-w64-x86_64-boost
>> mingw64/mingw-w64-x86_64-gettext mingw64/mingw-w64-x86_64-libiconv
>> mingw64/mingw-w64-x86_64-libidn mingw64/mingw-w64-x86_64-lua
Maybe you need mingw-w64-x86_64-lua51?
> 
>> mingw64/mingw-w64-x86_64-pcre mingw64/mingw-w64-x86_64-pkgconf
>> mingw64/mingw-w64-x86_64-sqlite3 mingw64/mingw-w64-x86_64-zlib
> 
> I installed mingw-w64-x86_64-toolchain, which includes several of the
> above.
> 
> I could not find out which package actually installs g++; 'pacman -Qo
> g++' gives 'error: No package owns /usr/mingw64/bin/g++'. So I don't
> know how to minimize the number of packages installed (not critical).
g++ is installed by mingw-w64-x86_64-gcc package.
> 
>> .. then we need to build botan. I hoped we had botan already as a
>> package (I guess you compiled it already?) but it seems not, and my
>> quick attempt to build it failed:
> 
> I had no problems with botan once I fixed the directory separators in
> configure.
> 
> I'm currently stuck running configure for monotone; it's giving several
> odd errors.
> 
> -- 
> -- Stephe
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Ray D. <min...@gm...>]

It may be that you need to get the latest config.sub and config.guess from
savannah that includes msys2 detection. I must go to bed but we'll pick up
again tomorrow.
On Apr 30, 2014 2:39 AM, "Stephen Leake" <ste...@st...>
wrote:

> Ray Donnelly <min...@gm...> writes:
>
> > Your goal is to build monotone for native Windows 64bit?
>
> Yes.
>
> > Here's a rundown of the steps I tried:
> >
> > Download and unpack msys2-base-x86_64-20140216.tar.xz, I'm going to do
> > this to E:\monotone and pretend you did the same just to simplify the
> > instructions.
>
> I installed to c:\msys2
>
> One possible complication: I have Cygwin installed at c:\, so /bin is
> the Cygwin bin.  But that doesn't seem to be a problem so far.
>
> > Since you want to build Win64 software, you should run
> > E:\monotone\msys64\mingw64_shell.bat
> > .. It will create the initial environment.
> > $ exit
> > run E:\monotone\msys64\mingw64_shell.bat
> > $ pacman -Syu
> > it will update the core system causing DLL address conflicts and we
> > need to rebase the MSYS dlls.
> > $ exit
> > wait for bash to go away (can take 20-30 seconds), then run
> > E:\monotone\msys64\autorebase.bat then run
> > E:\monotone\msys64\mingw64_shell.bat
>
> same as my list so far.
>
> > .. install base development tools:
> > $ pacman -S base-devel tar
> > $ exit
> > wait for bash to go away again then run
> > E:\monotone\msys64\autorebase.bat again then run
> > E:\monotone\msys64\mingw64_shell.bat again. Since we'll not update any
> > more MSYS DLLs this should be the last time we need to do this.
> > .. install monotone dependencies which I guess are:
> > $ pacman -S mingw-w64-x86_64-toolchain mingw64/mingw-w64-x86_64-boost
> > mingw64/mingw-w64-x86_64-gettext mingw64/mingw-w64-x86_64-libiconv
> > mingw64/mingw-w64-x86_64-libidn mingw64/mingw-w64-x86_64-lua
> > mingw64/mingw-w64-x86_64-pcre mingw64/mingw-w64-x86_64-pkgconf
> > mingw64/mingw-w64-x86_64-sqlite3 mingw64/mingw-w64-x86_64-zlib
>
> I installed mingw-w64-x86_64-toolchain, which includes several of the
> above.
>
> I could not find out which package actually installs g++; 'pacman -Qo
> g++' gives 'error: No package owns /usr/mingw64/bin/g++'. So I don't
> know how to minimize the number of packages installed (not critical).
>
> > .. then we need to build botan. I hoped we had botan already as a
> > package (I guess you compiled it already?) but it seems not, and my
> > quick attempt to build it failed:
>
> I had no problems with botan once I fixed the directory separators in
> configure.
>
> I'm currently stuck running configure for monotone; it's giving several
> odd errors.
>
> --
> -- Stephe
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users
>

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Ray Donnelly <min...@gm...> writes:

> It may be that you need to get the latest config.sub and config.guess from
> savannah that includes msys2 detection. 

That would help, but it's not hard specifying --build=. 

One problem I have is I prefer to run bash under Emacs, but I'm
apparently not setting up msys2 bash in the same way that
msys2_shell.bat does, because I get different results when I run under
Emacs vs in msys2_shell.bat. I'll read thru msys2_shell.bat again ...

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Ray D. <min...@gm...>]

I think if you set MSYSTEM=MSYS and called bash with the arguments "-i
--login" then that might be enough to get the same environment, Alexey
will know better though.

On Wed, Apr 30, 2014 at 8:03 AM, Stephen Leake
<ste...@st...> wrote:
> Ray Donnelly <min...@gm...> writes:
>
>> It may be that you need to get the latest config.sub and config.guess from
>> savannah that includes msys2 detection.
>
> That would help, but it's not hard specifying --build=.
>
> One problem I have is I prefer to run bash under Emacs, but I'm
> apparently not setting up msys2 bash in the same way that
> msys2_shell.bat does, because I get different results when I run under
> Emacs vs in msys2_shell.bat. I'll read thru msys2_shell.bat again ...
>
> --
> -- Stephe
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Ray Donnelly <min...@gm...> writes:

> I think if you set MSYSTEM=MSYS and called bash with the arguments "-i
> --login" then that might be enough to get the same environment, 

I was not doing "-i --login". I had actually figured that out for msys,
but didn't set things up clearly enough in my emacs config to remember
it. Sigh.

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Ray D. <min...@gm...>]

Indeed.

MSYS2 programs link to the msys dll, yes, and that performs the path
conversions at the right times yes, so when a program asks to spawn
another program, msys2 intercepts and translates the MSYS2 paths it
sees (sometimes it guesses this wrong) to Windows paths, iff the
program to run is *not* another MSYS2 program (which doesn't need or
want native Windows paths). This is one of the key things that MSYS2
does and Cygwin does not do, it's a part of MSYS2's sympathy for the
Windows OS.


On Wed, Apr 30, 2014 at 8:06 AM, Ray Donnelly <min...@gm...> wrote:
> I think if you set MSYSTEM=MSYS and called bash with the arguments "-i
> --login" then that might be enough to get the same environment, Alexey
> will know better though.
>
> On Wed, Apr 30, 2014 at 8:03 AM, Stephen Leake
> <ste...@st...> wrote:
>> Ray Donnelly <min...@gm...> writes:
>>
>>> It may be that you need to get the latest config.sub and config.guess from
>>> savannah that includes msys2 detection.
>>
>> That would help, but it's not hard specifying --build=.
>>
>> One problem I have is I prefer to run bash under Emacs, but I'm
>> apparently not setting up msys2 bash in the same way that
>> msys2_shell.bat does, because I get different results when I run under
>> Emacs vs in msys2_shell.bat. I'll read thru msys2_shell.bat again ...
>>
>> --
>> -- Stephe
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
>> unparalleled scalability from the best Selenium testing platform available.
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> Msys2-users mailing list
>> Msy...@li...
>> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Ray Donnelly <min...@gm...> writes:

> MSYS2 programs link to the msys dll, yes, and that performs the path
> conversions at the right times yes, so when a program asks to spawn
> another program, msys2 intercepts and translates the MSYS2 paths it
> sees (sometimes it guesses this wrong) to Windows paths, iff the
> program to run is *not* another MSYS2 program (which doesn't need or
> want native Windows paths). This is one of the key things that MSYS2
> does and Cygwin does not do, it's a part of MSYS2's sympathy for the
> Windows OS.

Let me try to interpret the currently failing configure test in
light of this.

Simplified, the command line that is failing is:

g++ -v -c -I/Msys2/msys64/include conftest.cpp

Here I'm trying to tell g++ where pcre.h is; it's not in one of the
standard include dirs that g++ uses (a separate issue in itself ;).

The relevant part of the g++ output is (comments interspersed):

COLLECT_GCC_OPTIONS='-v' '-c' '-I' 'C:/Msys2/msys64/Msys2/msys64/include' '-shared-libgcc' '-mtune=generic' '-march=x86-64'

    the -I path "/Msys2/msys64/include" has been changed to
    "C:/Msys2/msys64/Msys2/msys64/include" - NOT what I wanted.

ignoring nonexistent directory "C:/Msys2/msys64/Msys2/msys64/include"

    This is due to the erroneous path change above


There are two possible fixes here;

1) include c:/ in all absolute Windows paths (ie
   "c:/Msys2/msys64/include"), so msys2 knows it is an absolute path,
   and won't change it

2) use msys2 paths when the path is inside an msys2 mounted directory
   tree (ie "-I/usr/include"), so the change msys2 makes to the path is
   correct.


The erroneous change above was done by bash, before g++ was spawned. But when g++
spawns cpp.exe, the msys2 dll does a similar path conversion. So all
paths at that point had better include c:/, or not be in a msys2 mounted
directory tree.

--
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Alexey P. <ale...@gm...>]

30 апр. 2014 г., в 12:15, Stephen Leake <ste...@st...> написал(а):

> Ray Donnelly <min...@gm...> writes:
> 
>> MSYS2 programs link to the msys dll, yes, and that performs the path
>> conversions at the right times yes, so when a program asks to spawn
>> another program, msys2 intercepts and translates the MSYS2 paths it
>> sees (sometimes it guesses this wrong) to Windows paths, iff the
>> program to run is *not* another MSYS2 program (which doesn't need or
>> want native Windows paths). This is one of the key things that MSYS2
>> does and Cygwin does not do, it's a part of MSYS2's sympathy for the
>> Windows OS.
> 
> Let me try to interpret the currently failing configure test in
> light of this.
> 
> Simplified, the command line that is failing is:
> 
> g++ -v -c -I/Msys2/msys64/include conftest.cpp
> 
You need to have «-I/msys64/include» 

Regards,
Alexey.
> Here I'm trying to tell g++ where pcre.h is; it's not in one of the
> standard include dirs that g++ uses (a separate issue in itself ;).
> 
> The relevant part of the g++ output is (comments interspersed):
> 
> COLLECT_GCC_OPTIONS='-v' '-c' '-I' 'C:/Msys2/msys64/Msys2/msys64/include' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
> 
>    the -I path "/Msys2/msys64/include" has been changed to
>    "C:/Msys2/msys64/Msys2/msys64/include" - NOT what I wanted.
> 
> ignoring nonexistent directory "C:/Msys2/msys64/Msys2/msys64/include"
> 
>    This is due to the erroneous path change above
> 
> 
> There are two possible fixes here;
> 
> 1) include c:/ in all absolute Windows paths (ie
>   "c:/Msys2/msys64/include"), so msys2 knows it is an absolute path,
>   and won't change it
> 
> 2) use msys2 paths when the path is inside an msys2 mounted directory
>   tree (ie "-I/usr/include"), so the change msys2 makes to the path is
>   correct.
> 
> 
> The erroneous change above was done by bash, before g++ was spawned. But when g++
> spawns cpp.exe, the msys2 dll does a similar path conversion. So all
> paths at that point had better include c:/, or not be in a msys2 mounted
> directory tree.
> 
> --
> -- Stephe
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Alexey P. <al...@gm...>]

2014-04-30 11:25 GMT+03:00 Alexey Pavlov <ale...@gm...>:
>
> 30 апр. 2014 г., в 12:15, Stephen Leake <ste...@st...> написал(а):
>
>> Ray Donnelly <min...@gm...> writes:
>>
>>> MSYS2 programs link to the msys dll, yes, and that performs the path
>>> conversions at the right times yes, so when a program asks to spawn
>>> another program, msys2 intercepts and translates the MSYS2 paths it
>>> sees (sometimes it guesses this wrong) to Windows paths, iff the
>>> program to run is *not* another MSYS2 program (which doesn't need or
>>> want native Windows paths). This is one of the key things that MSYS2
>>> does and Cygwin does not do, it's a part of MSYS2's sympathy for the
>>> Windows OS.
>>
>> Let me try to interpret the currently failing configure test in
>> light of this.
>>
>> Simplified, the command line that is failing is:
>>
>> g++ -v -c -I/Msys2/msys64/include conftest.cpp
>>
> You need to have «-I/msys64/include»

Hmm. Seems something wrong with your include paths.
To help you I need to know next things:
1. You use mingw compiler to build or msys compiler.
2. Show me your msys2 directory organization.

>
> Regards,
> Alexey.
>> Here I'm trying to tell g++ where pcre.h is; it's not in one of the
>> standard include dirs that g++ uses (a separate issue in itself ;).
>>
>> The relevant part of the g++ output is (comments interspersed):
>>
>> COLLECT_GCC_OPTIONS='-v' '-c' '-I' 'C:/Msys2/msys64/Msys2/msys64/include' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
>>
>>    the -I path "/Msys2/msys64/include" has been changed to
>>    "C:/Msys2/msys64/Msys2/msys64/include" - NOT what I wanted.
>>
>> ignoring nonexistent directory "C:/Msys2/msys64/Msys2/msys64/include"
>>
>>    This is due to the erroneous path change above
>>
>>
>> There are two possible fixes here;
>>
>> 1) include c:/ in all absolute Windows paths (ie
>>   "c:/Msys2/msys64/include"), so msys2 knows it is an absolute path,
>>   and won't change it
>>
>> 2) use msys2 paths when the path is inside an msys2 mounted directory
>>   tree (ie "-I/usr/include"), so the change msys2 makes to the path is
>>   correct.
>>
>>
>> The erroneous change above was done by bash, before g++ was spawned. But when g++
>> spawns cpp.exe, the msys2 dll does a similar path conversion. So all
>> paths at that point had better include c:/, or not be in a msys2 mounted
>> directory tree.
>>
>> --
>> -- Stephe
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
>> unparalleled scalability from the best Selenium testing platform available.
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> Msys2-users mailing list
>> Msy...@li...
>> https://lists.sourceforge.net/lists/listinfo/msys2-users
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Stephen Leake <ste...@st...> writes:


> There are two possible fixes here;
>
> 1) include c:/ in all absolute Windows paths (ie
>    "c:/Msys2/msys64/include"), so msys2 knows it is an absolute path,
>    and won't change it
>
> 2) use msys2 paths when the path is inside an msys2 mounted directory
>    tree (ie "-I/usr/include"), so the change msys2 makes to the path is
>    correct.

with these fixes and "-i --login" applied, monotone configure now runs
to completion.

Now I'm running into "sizeof int == sizeof pointer, right?" errors.
Sigh.

--
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Alexey P. <al...@gm...>]

2014-04-30 11:44 GMT+03:00 Stephen Leake <ste...@st...>:
> Stephen Leake <ste...@st...> writes:
>
>
>> There are two possible fixes here;
>>
>> 1) include c:/ in all absolute Windows paths (ie
>>    "c:/Msys2/msys64/include"), so msys2 knows it is an absolute path,
>>    and won't change it
>>
>> 2) use msys2 paths when the path is inside an msys2 mounted directory
>>    tree (ie "-I/usr/include"), so the change msys2 makes to the path is
>>    correct.
>
> with these fixes and "-i --login" applied, monotone configure now runs
> to completion.
>
> Now I'm running into "sizeof int == sizeof pointer, right?" errors.
> Sigh.
>
I see you include MSYS2 includes instead MINGW includes. You can do it
only if you build monotone with MSYS-gcc

> --
> -- Stephe
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users

Re: [Msys2-users] symlinks vs configure vs gcc

[Stephen L. <ste...@st...>]

Alexey Pavlov <al...@gm...> writes:

> I see you include MSYS2 includes instead MINGW includes. You can do it
> only if you build monotone with MSYS-gcc

I was confused about which pcre package to install; it is now the mingw one.

-- 
-- Stephe

Re: [Msys2-users] symlinks vs configure vs gcc

[Alexpux <al...@gm...>]

30 апр. 2014 г., в 22:58, Stephen Leake <ste...@st...> написал(а):

> Alexey Pavlov <al...@gm...> writes:
> 
>> I see you include MSYS2 includes instead MINGW includes. You can do it
>> only if you build monotone with MSYS-gcc
> 
> I was confused about which pcre package to install; it is now the mingw one.
> 
This is because you don’t answer for my questions. I can’t help you if you just write what you want without dealing with us.

Regards,
Alexey.
> -- 
> -- Stephe
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users