>> It seems that it is necessary to have certain mingw libraries. However, >> those libraries - as far as i know - themselves need msys to mingw >> cross-compiler to be compiled. Is there a correct build order or sequence >> to build all those things starting from "bare" msys?
> Why don't you install those libraries with pacman? That would defeat the purpose. I am trying to build from source as much as possible. If there is a way to build cross compiler without installing further pre-built packages, i would like to take it. > And why do you need a msys2->mingw-w64 cross-compiler at all? Why don't > use the native mingw-w64 compiler that MSYS2 provides? Same answer as before. In fact, in need the cross sompiler to build native compiler from latest gcc sources. > (BTW, when asking this type of questions always show the commands you > executed) As i was saying, i was following PKGBUILD, although without forming a package. So my commands for build were: ../configure --prefix=/opt --build=x86_64-pc-msys --host=x86_64-pc-msys --target=x86_64-w64-mingw32 --libexecdir=/opt/lib --disable-bootstrap --with-arch=x86-64 --with-tune=generic --enable-languages=c,c++,fortran,lto --enable-shared --enable-static --enable-threads=win32 --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-isl-version-check --enable-lto --enable-libgomp --disable-multilib --enable-checking=release --disable-rpath --disable-win32-registry --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/usr --with-mpfr=/usr --with-mpc=/usr --with-isl=/usr --with-gnu-as --with-gnu-ld CFLAGS="-O2 -pipe" CXXFLAGS="-O2 -pipe" make the commands were run from an added "build" subfolder in patched source.
_______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
