Closed class101 closed 10 years ago
Initial .configure output
ct-ng:/root/crosstool-ng-darwin-svn/.build/i686-apple-darwin10/build/build-cctools-host-i686-build_pc-cygwin> LDFLAGS="-L/root/gcc-i686-apple-darwin10/lib -L/root/gcc-i686-apple-darwin10/i686-apple-darwin10/sysroot/usr/lib" CFLAGS="-O2 -g -pipe -I/root/crosstool-ng-darwin-svn/.build/i686-apple-darw
in10/buildtools/include/ -D__DARWIN_UNIX03 -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -I/root/gcc-i686-apple-darwin10/include -fno-builtin-round -fno-builtin-trunc" /root/crosstool-ng-darwin-svn/.build/src/cctools-809/configure --build=i686-build_pc-cygwin --host=i686-build_pc-cygwin --target=i
686-apple-darwin10 --prefix=/root/gcc-i686-apple-darwin10 --with-llvm=/root/gcc-i686-apple-darwin10 --disable-static --enable-shared --with-sysroot=/root/gcc-i686-apple-darwin10/i686-apple-darwin10/sysroot
checking for i686-build_pc-cygwin-gcc... i686-build_pc-cygwin-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-build_pc-cygwin-gcc accepts -g... yes
checking for i686-build_pc-cygwin-gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... i686-build_pc-cygwin-gcc -E
checking for grep that handles long lines and -e... /root/crosstool-ng-darwin-svn/.build/tools/bin/grep
checking for egrep... /root/crosstool-ng-darwin-svn/.build/tools/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for a BSD-compatible install... /root/crosstool-ng-darwin-svn/.build/tools/bin/install -c
checking whether ln -s works... yes
checking for i686-build_pc-cygwin-gcc... (cached) i686-build_pc-cygwin-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether i686-build_pc-cygwin-gcc accepts -g... (cached) yes
checking for i686-build_pc-cygwin-gcc option to accept ISO C89... (cached) none needed
checking for i686-build_pc-cygwin-g++... i686-build_pc-cygwin-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i686-build_pc-cygwin-g++ accepts -g... yes
checking for i686-build_pc-cygwin-gcc option to accept ISO C99... -std=gnu99
checking build system type... i686-build_pc-cygwin
checking host system type... i686-build_pc-cygwin
checking target system type... i686-apple-darwin10
checking whether C compiler accepts ... yes
checking whether C compiler accepts -D__DARWIN_UNIX03... yes
checking whether C compiler accepts -D__STDC_LIMIT_MACROS... yes
checking whether C compiler accepts -D__STDC_CONSTANT_MACROS... yes
checking whether C compiler accepts -D__DARWIN_UNIX03... (cached) yes
checking whether C compiler accepts -D__STDC_LIMIT_MACROS... (cached) yes
checking whether C compiler accepts -D__STDC_CONSTANT_MACROS... (cached) yes
checking libc.h usability... no
checking libc.h presence... no
checking for libc.h... no
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking err.h usability... yes
checking err.h presence... yes
checking for err.h... yes
checking execinfo.h usability... no
checking execinfo.h presence... no
checking for execinfo.h... no
checking sys/cdefs.h usability... yes
checking sys/cdefs.h presence... yes
checking for sys/cdefs.h... yes
checking sys/_endian.h usability... no
checking sys/_endian.h presence... no
checking for sys/_endian.h... no
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking sys/sysctl.h usability... no
checking sys/sysctl.h presence... no
checking for sys/sysctl.h... no
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking servers/bootstrap.h usability... no
checking servers/bootstrap.h presence... no
checking for servers/bootstrap.h... no
checking malloc/malloc.h usability... no
checking malloc/malloc.h presence... no
checking for malloc/malloc.h... no
checking configure.h usability... no
checking configure.h presence... no
checking for configure.h... no
checking tzfile.h usability... yes
checking tzfile.h presence... yes
checking for tzfile.h... yes
checking CommonCrypto/CommonDigest.h usability... no
checking CommonCrypto/CommonDigest.h presence... no
checking for CommonCrypto/CommonDigest.h... no
checking for uid_t in sys/types.h... yes
checking for caddr_t... yes
checking for sigset_t... yes
checking for u_int32_t... yes
checking for u_char... yes
checking for u_short... yes
checking for u_int... yes
checking whether MIN is declared... yes
checking whether sleep is declared... yes
checking whether SIGHUP is declared... yes
checking whether SIGPIPE is declared... yes
checking for dl_info... no
checking whether O_BINARY is declared... yes
checking for bcmp... yes
checking for bcopy... yes
checking for bzero... yes
checking for setbuffer... yes
checking for getwd... yes
checking for ffs... yes
checking for getc_unlocked... yes
checking whether ULLONG_MAX is declared... yes
checking for CTL_KERN in sys/sysctl.h... no
checking for KERN_OSRELEASE in sys/sysctl.h... no
checking whether __unused is declared... yes
checking whether FP_PREC_24B is declared... no
checking whether FP_PREC_53B is declared... no
checking whether FP_PREC_64B is declared... no
checking whether FP_RND_NEAR is declared... no
checking whether FP_RND_DOWN is declared... no
checking whether FP_RND_UP is declared... no
checking whether FP_CHOP is declared... no
checking whether S_IFSOCK is declared... yes
checking whether S_ISUID is declared... yes
checking whether S_IFLNK is declared... yes
checking whether S_IRGRP is declared... yes
checking whether S_IWGRP is declared... yes
checking whether S_IXGRP is declared... yes
checking whether S_ISGID is declared... yes
checking whether S_IROTH is declared... yes
checking whether S_IWOTH is declared... yes
checking whether S_IXOTH is declared... yes
checking whether S_ISVTX is declared... yes
checking whether EBADRPC is declared... no
checking whether EFTYPE is declared... yes
checking whether CPU_SUBTYPE_ARM_V5TEJ is declared... no
checking whether CPU_SUBTYPE_ARM_XSCALE is declared... no
checking whether CPU_SUBTYPE_ARM_V7 is declared... no
checking whether N_ARM_THUMB_DEF is declared... no
checking for i686-build_pc-cygwin-ranlib... i686-build_pc-cygwin-ranlib
checking for i686-build_pc-cygwin-ar... i686-build_pc-cygwin-ar
checking for configured assembler targets... ppc ppc64 i386 x86_64 arm
configure: "Using llvm in prefix /root/gcc-i686-apple-darwin10"
checking whether C compiler accepts -I/root/gcc-i686-apple-darwin10/include... yes
checking whether C compiler accepts -L/root/gcc-i686-apple-darwin10/lib... yes
checking whether C compiler accepts -mdynamic-no-pic... no
checking whether C compiler accepts -fno-builtin-round... yes
checking whether C compiler accepts -fno-builtin-trunc... yes
checking if -no-cpp-precomp is supported... no
checking whether C compiler accepts -Wimport... yes
checking whether C compiler accepts -Wunused-variable... yes
checking whether C compiler accepts -Wunused-but-set-variable... yes
checking whether C compiler accepts -Wdeprecated-declarations... yes
checking if __private_extern__ is supported... no
checking if -multiply_defined suppress is supported... no
checking whether C++ compiler accepts -Wtrigraphs... yes
checking whether C++ compiler accepts -Wdeprecated... yes
checking whether C++ compiler accepts -Wstrict-aliasing... yes
checking whether C++ compiler accepts -Wenum-compare... yes
checking whether C++ compiler accepts -Winvalid-offsetof... yes
checking for qsort_r... no
checking for qsort... yes
checking for getattrlist... no
checking for NSIsSymbolNameDefined... no
checking for strlcpy... yes
checking for strlcat... yes
checking for _NSGetExecutablePath... no
checking whether vm_msync is declared... no
checking whether backtrace is declared... no
checking whether dlopen is declared... yes
checking whether dlsym is declared... yes
checking whether dlclose is declared... yes
checking whether dlerror is declared... yes
checking whether dladdr is declared... no
checking whether mmap is declared... yes
checking whether flock is declared... yes
checking whether sigfillset is declared... yes
checking whether sigprocmask is declared... yes
checking whether utimes is declared... yes
checking whether asprintf is declared... yes
checking whether strlcpy is declared... yes
checking whether strlcat is declared... yes
checking whether rindex is declared... yes
checking whether index is declared... yes
checking whether strmode is declared... no
checking whether mkstemp is declared... yes
checking whether fchmod is declared... yes
checking whether fchdir is declared... yes
checking whether pwrite is declared... yes
checking whether realpath is declared... yes
checking whether readlink is declared... yes
checking whether getuid is declared... yes
checking whether getgid is declared... yes
checking whether byte ordering is bigendian... no
checking for uuid_generate_random... no
checking for uuid_generate_random in -luuid... yes
checking for dlopen... yes
checking for lto_get_version in -lLTO... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating include/Makefile
config.status: creating libprunetrie/Makefile
config.status: creating libstuff/Makefile
config.status: creating libmacho/Makefile
config.status: creating ar/Makefile
config.status: creating as/Makefile
config.status: creating as/ppc/Makefile
config.status: creating as/ppc64/Makefile
config.status: creating as/i386/Makefile
config.status: creating as/x86_64/Makefile
config.status: creating as/arm/Makefile
config.status: creating ld/Makefile
config.status: creating ld64/Makefile
config.status: creating man/Makefile
config.status: creating misc/Makefile
config.status: creating otool/Makefile
config.status: creating include/config.h
config.status: include/config.h is unchanged
config.status: creating include/libc.h
config.status: include/libc.h is unchanged
config.status: creating include/libc_cxx.h
config.status: include/libc_cxx.h is unchanged
config.status: creating include/execinfo.h
config.status: include/execinfo.h is unchanged
config.status: creating include/sys/_endian.h
config.status: include/sys/_endian.h is unchanged
config.status: creating include/sys/sysctl.h
config.status: include/sys/sysctl.h is unchanged
config.status: creating include/servers/bootstrap.h
config.status: include/servers/bootstrap.h is unchanged
config.status: creating include/malloc/malloc.h
config.status: include/malloc/malloc.h is unchanged
config.status: creating include/configure.h
config.status: include/configure.h is unchanged
config.status: creating include/CommonCrypto/CommonDigest.h
config.status: include/CommonCrypto/CommonDigest.h is unchanged
Cygwin is not a platform that we currently support.
We do however, support native Windows via MinGW-w64. Is there any reason to prefer Cygwin to native?
On Thu, Jan 9, 2014 at 3:16 PM, Arnaud.Dovi notifications@github.comwrote:
Initial .configure output
ct-ng:/root/crosstool-ng-darwin-svn/.build/i686-apple-darwin10/build/build-cctools-host-i686-build_pc-cygwin> LDFLAGS="-L/root/gcc-i686-apple-darwin10/lib -L/root/gcc-i686-apple-darwin10/i686-apple-darwin10/sysroot/usr/lib" CFLAGS="-O2 -g -pipe -I/root/crosstool-ng-darwin-svn/.build/i686-apple-darw in10/buildtools/include/ -DDARWIN_UNIX03 -DSTDC_LIMIT_MACROS -DSTDC_CONSTANT_MACROS -I/root/gcc-i686-apple-darwin10/include -fno-builtin-round -fno-builtin-trunc" /root/crosstool-ng-darwin-svn/.build/src/cctools-809/configure --build=i686-build_pc-cygwin --host=i686-build_pc-cygwin --target=i 686-apple-darwin10 --prefix=/root/gcc-i686-apple-darwin10 --with-llvm=/root/gcc-i686-apple-darwin10 --disable-static --enable-shared --with-sysroot=/root/gcc-i686-apple-darwin10/i686-apple-darwin10/sysroot checking for i686-build_pc-cygwin-gcc... i686-build_pc-cygwin-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-build_pc-cygwin-gcc accepts -g... yes checking for i686-build_pc-cygwin-gcc option to accept ISO C89... none needed checking how to run the C preprocessor... i686-build_pc-cygwin-gcc -E checking for grep that handles long lines and -e... /root/crosstool-ng-darwin-svn/.build/tools/bin/grep checking for egrep... /root/crosstool-ng-darwin-svn/.build/tools/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define EXTENSIONS... yes checking for a BSD-compatible install... /root/crosstool-ng-darwin-svn/.build/tools/bin/install -c checking whether ln -s works... yes checking for i686-build_pc-cygwin-gcc... (cached) i686-build_pc-cygwin-gcc checking whether we are using the GNU C compiler... (cached) yes checking whether i686-build_pc-cygwin-gcc accepts -g... (cached) yes checking for i686-build_pc-cygwin-gcc option to accept ISO C89... (cached) none needed checking for i686-build_pc-cygwin-g++... i686-build_pc-cygwin-g++ checking whether we are using the GNU C++ compiler... yes checking whether i686-build_pc-cygwin-g++ accepts -g... yes checking for i686-build_pc-cygwin-gcc option to accept ISO C99... -std=gnu99 checking build system type... i686-build_pc-cygwin checking host system type... i686-build_pc-cygwin checking target system type... i686-apple-darwin10 checking whether C compiler accepts ... yes checking whether C compiler accepts -DDARWIN_UNIX03... yes checking whether C compiler accepts -DSTDC_LIMIT_MACROS... yes checking whether C compiler accepts -DSTDC_CONSTANT_MACROS... yes checking whether C compiler accepts -DDARWIN_UNIX03... (cached) yes checking whether C compiler accepts -DSTDC_LIMIT_MACROS... (cached) yes checking whether C compiler accepts -DSTDC_CONSTANT_MACROS... (cached) yes checking libc.h usability... no checking libc.h presence... no checking for libc.h... no checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking err.h usability... yes checking err.h presence... yes checking for err.h... yes checking execinfo.h usability... no checking execinfo.h presence... no checking for execinfo.h... no checking sys/cdefs.h usability... yes checking sys/cdefs.h presence... yes checking for sys/cdefs.h... yes checking sys/_endian.h usability... no checking sys/_endian.h presence... no checking for sys/_endian.h... no checking sys/mman.h usability... yes checking sys/mman.h presence... yes checking for sys/mman.h... yes checking sys/sysctl.h usability... no checking sys/sysctl.h presence... no checking for sys/sysctl.h... no checking paths.h usability... yes checking paths.h presence... yes checking for paths.h... yes checking servers/bootstrap.h usability... no checking servers/bootstrap.h presence... no checking for servers/bootstrap.h... no checking malloc/malloc.h usability... no checking malloc/malloc.h presence... no checking for malloc/malloc.h... no checking configure.h usability... no checking configure.h presence... no checking for configure.h... no checking tzfile.h usability... yes checking tzfile.h presence... yes checking for tzfile.h... yes checking CommonCrypto/CommonDigest.h usability... no checking CommonCrypto/CommonDigest.h presence... no checking for CommonCrypto/CommonDigest.h... no checking for uid_t in sys/types.h... yes checking for caddr_t... yes checking for sigset_t... yes checking for u_int32_t... yes checking for u_char... yes checking for u_short... yes checking for u_int... yes checking whether MIN is declared... yes checking whether sleep is declared... yes checking whether SIGHUP is declared... yes checking whether SIGPIPE is declared... yes checking for dl_info... no checking whether O_BINARY is declared... yes checking for bcmp... yes checking for bcopy... yes checking for bzero... yes checking for setbuffer... yes checking for getwd... yes checking for ffs... yes checking for getc_unlocked... yes checking whether ULLONG_MAX is declared... yes checking for CTL_KERN in sys/sysctl.h... no checking for KERN_OSRELEASE in sys/sysctl.h... no checking whether unused is declared... yes checking whether FP_PREC_24B is declared... no checking whether FP_PREC_53B is declared... no checking whether FP_PREC_64B is declared... no checking whether FP_RND_NEAR is declared... no checking whether FP_RND_DOWN is declared... no checking whether FP_RND_UP is declared... no checking whether FP_CHOP is declared... no checking whether S_IFSOCK is declared... yes checking whether S_ISUID is declared... yes checking whether S_IFLNK is declared... yes checking whether S_IRGRP is declared... yes checking whether S_IWGRP is declared... yes checking whether S_IXGRP is declared... yes checking whether S_ISGID is declared... yes checking whether S_IROTH is declared... yes checking whether S_IWOTH is declared... yes checking whether S_IXOTH is declared... yes checking whether S_ISVTX is declared... yes checking whether EBADRPC is declared... no checking whether EFTYPE is declared... yes checking whether CPU_SUBTYPE_ARM_V5TEJ is declared... no checking whether CPU_SUBTYPE_ARM_XSCALE is declared... no checking whether CPU_SUBTYPE_ARM_V7 is declared... no checking whether N_ARM_THUMB_DEF is declared... no checking for i686-build_pc-cygwin-ranlib... i686-build_pc-cygwin-ranlib checking for i686-build_pc-cygwin-ar... i686-build_pc-cygwin-ar checking for configured assembler targets... ppc ppc64 i386 x86_64 arm configure: "Using llvm in prefix /root/gcc-i686-apple-darwin10" checking whether C compiler accepts -I/root/gcc-i686-apple-darwin10/include... yes checking whether C compiler accepts -L/root/gcc-i686-apple-darwin10/lib... yes checking whether C compiler accepts -mdynamic-no-pic... no checking whether C compiler accepts -fno-builtin-round... yes checking whether C compiler accepts -fno-builtin-trunc... yes checking if -no-cpp-precomp is supported... no checking whether C compiler accepts -Wimport... yes checking whether C compiler accepts -Wunused-variable... yes checking whether C compiler accepts -Wunused-but-set-variable... yes checking whether C compiler accepts -Wdeprecated-declarations... yes checking if __private_extern__ is supported... no checking if -multiply_defined suppress is supported... no checking whether C++ compiler accepts -Wtrigraphs... yes checking whether C++ compiler accepts -Wdeprecated... yes checking whether C++ compiler accepts -Wstrict-aliasing... yes checking whether C++ compiler accepts -Wenum-compare... yes checking whether C++ compiler accepts -Winvalid-offsetof... yes checking for qsort_r... no checking for qsort... yes checking for getattrlist... no checking for NSIsSymbolNameDefined... no checking for strlcpy... yes checking for strlcat... yes checking for _NSGetExecutablePath... no checking whether vm_msync is declared... no checking whether backtrace is declared... no checking whether dlopen is declared... yes checking whether dlsym is declared... yes checking whether dlclose is declared... yes checking whether dlerror is declared... yes checking whether dladdr is declared... no checking whether mmap is declared... yes checking whether flock is declared... yes checking whether sigfillset is declared... yes checking whether sigprocmask is declared... yes checking whether utimes is declared... yes checking whether asprintf is declared... yes checking whether strlcpy is declared... yes checking whether strlcat is declared... yes checking whether rindex is declared... yes checking whether index is declared... yes checking whether strmode is declared... no checking whether mkstemp is declared... yes checking whether fchmod is declared... yes checking whether fchdir is declared... yes checking whether pwrite is declared... yes checking whether realpath is declared... yes checking whether readlink is declared... yes checking whether getuid is declared... yes checking whether getgid is declared... yes checking whether byte ordering is bigendian... no checking for uuid_generate_random... no checking for uuid_generate_random in -luuid... yes checking for dlopen... yes checking for lto_get_version in -lLTO... no configure: creating ./config.status config.status: creating Makefile config.status: creating include/Makefile config.status: creating libprunetrie/Makefile config.status: creating libstuff/Makefile config.status: creating libmacho/Makefile config.status: creating ar/Makefile config.status: creating as/Makefile config.status: creating as/ppc/Makefile config.status: creating as/ppc64/Makefile config.status: creating as/i386/Makefile config.status: creating as/x86_64/Makefile config.status: creating as/arm/Makefile config.status: creating ld/Makefile config.status: creating ld64/Makefile config.status: creating man/Makefile config.status: creating misc/Makefile config.status: creating otool/Makefile config.status: creating include/config.h config.status: include/config.h is unchanged config.status: creating include/libc.h config.status: include/libc.h is unchanged config.status: creating include/libc_cxx.h config.status: include/libc_cxx.h is unchanged config.status: creating include/execinfo.h config.status: include/execinfo.h is unchanged config.status: creating include/sys/_endian.h config.status: include/sys/_endian.h is unchanged config.status: creating include/sys/sysctl.h config.status: include/sys/sysctl.h is unchanged config.status: creating include/servers/bootstrap.h config.status: include/servers/bootstrap.h is unchanged config.status: creating include/malloc/malloc.h config.status: include/malloc/malloc.h is unchanged config.status: creating include/configure.h config.status: include/configure.h is unchanged config.status: creating include/CommonCrypto/CommonDigest.h config.status: include/CommonCrypto/CommonDigest.h is unchanged
Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-31940946 .
Because MinGW-w64 is a bit obscure to install under Windows, when I go to http://mingw-w64.sourceforge.net/ I'm presented with lots of packages I don't have a clue what to do with huhuh
I didn't know that you not support cygwin, Its just I did my i686 and x86_64-unknown-linux-gnu cross compiler under the official crosstool-ng with cygwin so I expected the fork to work with too but if you say you support mingw64 I will switch to it, just didn't know I'm not so familiar with the gnu compilers available on Windows so my choice was obvious to cygwin
Do you know any simple way to get this Mingw-w64 installed on Windows ?
I'm happy to provide prebuilt cross-compilers to you, but I'd be more happy to guide you through the process of setting up and building on MSYS2/MinGW-w64. If you are interested in this then initially you should get:
http://sourceforge.net/projects/msys2/files/Base/x86_64/msys2-base-x86_64-20131208.tar.xz/download
Let me know if you want to continue with this!
On Thu, Jan 9, 2014 at 5:50 PM, Arnaud.Dovi notifications@github.comwrote:
Because MinGW-w64 is a bit obscure to install under Windows, when I go to http://mingw-w64.sourceforge.net/ I'm presented with lots of packages I don't have a clue what to do with huhuh
I didn't know that you not support cygwin, Its just I did my i686 and x86_64-unknown-linux-gnu cross compiler under the official crosstool-ng with cygwin so I expected the fork to work with too but if you say you support mingw64 I will switch to it, just didn't know I'm not so familiar with the gnu compilers available on Windows so my choice was obvious to cygwin
Do you know any simple way to get this Mingw-w64 installed on Windows ?
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-31958228 .
Thanks you appreciate a lot your offer and help, yet I will try to do it alone so I can better understand hwow it is built, they are very interesting project crosstool-ng and this fork, keep it up =)
Ok, MSYS2 is the latest hotness (IMHO, but I help out on it a bit so I am biased).
Alexey Pavlov ported Arch Linux's Pacman package manager and we (mostly he) maintain(s) two sets of packages, ones for MSYS2 and ones for MinGW-w64 (i686 and x86_64). The aim is to bring the very cool easy package management and rolling releases of Arch Linux to the Windows world. There's only a few of us working on it so we are focused on our favourite packages for now (and essential build tools of course).
The only page of documentation (apart from the reams of sometimes relevant, often irrelevant Arch Linux stuff) so far is: http://sourceforge.net/p/msys2/wiki/MSYS2%20installation/
You'll want to install at least git, then get your hands on a good (one created with gnutar -h to ensure dereferencing of symlinks) Mac OS X SDK (10.6 is most tested, then 10.7).
Unpack the OS X SDK to $HOME/MacOSX10.6.sdk.
I have a wrapper project that wraps around crosstool-ng and includes some in-development patches for this project that I will be merging soon. I'd recommend using that initially, and studying it a little to get a grasp on what's needed for ctng on MSYS2/MinGW-w64:
git clone http://github.com/mingwandroid/ctng-firefox-builds -b ps3.wip cd ctng-firefox-builds ./build.sh --help or .. ./build.sh --target-os=osx
.. note, this is OSX, and not iPhone. Adding iPhone support is very easy, I've just not done it yet, let me know if this is what you need.
On Thu, Jan 9, 2014 at 5:57 PM, Arnaud.Dovi notifications@github.comwrote:
Thanks you appreciate a lot your offer and help, yet I will try to do it alone so I can better understand hwow it is built, they are very interesting project crosstool-ng and this fork, keep it up =)
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-31958874 .
wow indeed that's great you ported Pacman, installation is quick
yet I'm stuck on a strange issue, it refuses to configure llvm (tried head-git,3.3 and 2.7) seems to not recognize i686-build_pc-msys
[INFO ] Installing LLVM for host
[DEBUG] Entering '/root/crosstool-ng-darwin-svn/.build/i686-apple-darwin10/build/build-LLVM-host-i686-build_pc-msys'
[EXTRA] Configuring LLVM
[DEBUG] ==> Executing: 'CFLAGS=-O2 -g -pipe -m32' 'CXXFLAGS=-O2 -g -pipe -m32' 'LDFLAGS= -m32' './configure' '--build=i686-build_pc-msys' '--host=i686-build_pc-msys' '--prefix=/root/gcc-i686-apple-darwin10' '--target=i686-apple-darwin10' '--enable-optimized=yes'
[CFG ] checking build system type... i686-build_pc-msys
[CFG ] checking host system type... i686-build_pc-msys
[CFG ] checking target system type... i686-apple-darwin10
[CFG ] checking type of operating system we're going to host on... Unknown
[CFG ] checking type of operating system we're going to target... Darwin
[ERROR] configure: error: Operating system is unknown, configure can't continue
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Installing LLVM for host'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR] >> called from: do_llvm_backend[scripts/build/companion_libs/150-llvm.sh@135]
[ERROR] >> called from: do_llvm_for_host[scripts/build/companion_libs/150-llvm.sh@96]
[ERROR] >> called from: do_companion_libs_for_host[scripts/build/companion_libs.sh@36]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@683]
No. Again I don't care for the final tools being cygwin or MSYS 2. Only ctng itself is compiled as an MSYS 2 executable.
Please run my script. On Jan 9, 2014 7:52 PM, "Arnaud.Dovi" notifications@github.com wrote:
wow indeed that's great you ported Pacman, installation is quick
yet I'm stuck on a strange issue, it refuses to configure llvm (tried head-git,3.3 and 2.7) seems to not recognize i686-build_pc-msys
[INFO ] Installing LLVM for host [DEBUG] Entering '/root/crosstool-ng-darwin-svn/.build/i686-apple-darwin10/build/build-LLVM-host-i686-build_pc-msys' [EXTRA] Configuring LLVM [DEBUG] ==> Executing: 'CFLAGS=-O2 -g -pipe -m32' 'CXXFLAGS=-O2 -g -pipe -m32' 'LDFLAGS= -m32' './configure' '--build=i686-build_pc-msys' '--host=i686-build_pc-msys' '--prefix=/root/gcc-i686-apple-darwin10' '--target=i686-apple-darwin10' '--enable-optimized=yes' [CFG ] checking build system type... i686-build_pc-msys [CFG ] checking host system type... i686-build_pc-msys [CFG ] checking target system type... i686-apple-darwin10 [CFG ] checking type of operating system we're going to host on... Unknown [CFG ] checking type of operating system we're going to target... Darwin [ERROR] configure: error: Operating system is unknown, configure can't continue [ERROR] [ERROR] >> [ERROR] >> Build failed in step 'Installing LLVM for host' [ERROR] >> called in step '(top-level)' [ERROR] >> [ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257] [ERROR] >> called from: do_llvm_backend[scripts/build/companion_libs/150-llvm.sh@135] [ERROR] >> called from: do_llvm_for_host[scripts/build/companion_libs/150-llvm.sh@96] [ERROR] >> called from: do_companion_libs_for_host[scripts/build/companion_libs.sh@36] [ERROR] >> called from: main[scripts/crosstool-NG.sh@683]
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-31969123 .
I see missed that thank you I should have all now to do it thank you saves me so much time.
oops accidently pushed closed, I let you anyway decide when you want to close it
I don't mind really. One thing I spotted is that llvm-head no longer compiles (the joy of tracking svn/git repositories!), so you may want to switch it to v 3.3 or 3.4.
ATM 3.4 is fetched from a git branch which I hope hasn't been deleted yet. Anyway, 3.3 is in pretty good shape and is fetched from tarballs.
Overall, for now I'd recommend changing:
TARGET_LLVM_VERSIONS_osx="head"
To:
TARGET_LLVM_VERSIONS_osx="3.3"
In build.sh.
On Thu, Jan 9, 2014 at 8:16 PM, Arnaud.Dovi notifications@github.comwrote:
oops accidently pushed closed, I let you anyway decide when you want to close it
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-31971332 .
thank yes, btw small issue I got in the build.sh was when it attempted to
git clone git@github.com:diorcety/crosstool-ng.git
Got a permission denied, quickly solved by using the clone link I have from the http site
with build.sh I have passed all the errors I had but I have one near the end when it compiles the stage build-cc-gcc-final when it compiles fixincl.c at line 28 it complains the file sys/wait.h can't be found while it seems the make all as been able to complete the other lib libiberty, decnumber, libcpp.a, seems failing at fixincludes here
I just did you setup except I set 12 jobs instead of 1 and I have disabled clang, and the objective c languages llvm is 3.3 and other companion tools are latest version
I notice the default folder name is rather long x-o-3_3-apple_5666_3-x86_64-235295c4 I will set a shorter mount posix=1 in the fstab and link everything to smaller path, I may have a long file path bug
How did you disable clang and set the jobs to 12?
I assume as follows:
TARGET_LLVM_VERSIONS_osx="none" CT_JOBS=12
Is that right?
On Fri, Jan 10, 2014 at 1:03 PM, Arnaud.Dovi notifications@github.comwrote:
with build.sh I have passed all the errors I had but I have one near the end when it compiles the stage build-cc-gcc-final when it compiles fixincl.c at line 28 it complains the file sys/wait.h wan't be found while it seems the make all as been able to complete the other lib libiberty, decnumber, libcpp.a, seem failing at fixincludes here
I just did you setup except I set 12 jobs instead of 1 and I have disabled clang, and the objective c languages
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32025430 .
Oh, also,
CT_PARALLEL_JOBS=12
On Fri, Jan 10, 2014 at 1:13 PM, Ray Donnelly mingw.android@gmail.comwrote:
How did you disable clang and set the jobs to 12?
I assume as follows:
TARGET_LLVM_VERSIONS_osx="none" CT_JOBS=12
Is that right?
On Fri, Jan 10, 2014 at 1:03 PM, Arnaud.Dovi notifications@github.comwrote:
with build.sh I have passed all the errors I had but I have one near the end when it compiles the stage build-cc-gcc-final when it compiles fixincl.c at line 28 it complains the file sys/wait.h wan't be found while it seems the make all as been able to complete the other lib libiberty, decnumber, libcpp.a, seem failing at fixincludes here
I just did you setup except I set 12 jobs instead of 1 and I have disabled clang, and the objective c languages
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32025430 .
yes CT_PARALLEL_JOBS=12
and for disabling clang I have checked how is doing menuconfig and it seems to remove all the CT_CC_CLANG* occurence so I have removed them and after In the file is set "# CT_CC_clang is not set" placed automatically in the file
Also I have disabled the debugger gdb debugger as I will not need them under Windows
Ok, can you clarify that you are using build.sh from ctng-firefox-builds (ps3.wip branch)? I want to rule out all differences. Also, can you pastebin the build.sh as you have it for the same reason. We'll need to compare logs I think.
On Fri, Jan 10, 2014 at 1:30 PM, Arnaud.Dovi notifications@github.comwrote:
yes CT_PARALLEL_JOBS=12
and for disabling clang I have checked how is doing menuconfig and it seems to remove all the CT_CC_CLANG* occurence so I have a normal # CT_CC_clang is not set automatically put in the config file
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32027042 .
Sure
build.sh http://pastebin.com/p9S5dNBL
crosstool.config.osx.64 http://pastebin.com/up4ytANX
and my msys64/etc/fstab X:\LIBRARIES /root ntfs posix=1 0 0
To note when I crashed I had
BUILT_XCOMPILER_PREFIX=$PWD/${STUB}-${BUILD_PREFIX}
and
BUILDDIR=/root/tmp/ctng-build-${STUB}-${BUILD_PREFIX}
so I loaded a new test with hardcoded names wich you see on pastebin, hasn't finished yet
Well, I have run into the same issue just now! Weird. I will take a look after work.
On Fri, Jan 10, 2014 at 1:42 PM, Arnaud.Dovi notifications@github.comwrote:
Sure
build.sh http://pastebin.com/p9S5dNBL
crosstool.config.osx.64 http://pastebin.com/up4ytANX
and my msys64/etc/fstab X:\LIBRARIES /root ntfs posix=1 0 0
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32027758 .
Just got the same error, good luck on this one seems not evident to patch for a newbie like me, will let you know if I get any luck but I doubt
[INFO ] Installing final gcc compiler
[EXTRA] Configuring final gcc compiler
[EXTRA] Building final gcc compiler
[ERROR] ../../../../src/gcc-5666.3/fixincludes/fixincl.c:28:22: fatal error: sys/wait.h: No such file or directory
[ERROR] make[3]: *** [fixincl.o] Error 1
[ERROR] ../../../../../src/gcc-5666.3/fixincludes/fixincl.c:28:22: fatal error: sys/wait.h: No such file or directory
[ERROR] make[3]: *** [fixincl.o] Error 1
[ERROR] make[2]: *** [all-build-fixincludes] Error 2
[ERROR] make[2]: *** [all-fixincludes] Error 2
[38:33] -
It'll be easy enough. It rings a bell! On Jan 10, 2014 2:17 PM, "Arnaud.Dovi" notifications@github.com wrote:
Just got the same error, good luck on this one seems not evident to patch for a newbie like me
[INFO ] Installing final gcc compiler [EXTRA] Configuring final gcc compiler [EXTRA] Building final gcc compiler [ERROR] ../../../../src/gcc-5666.3/fixincludes/fixincl.c:28:22: fatal error: sys/wait.h: No such file or directory [ERROR] make[3]: * [fixincl.o] Error 1 [ERROR] ../../../../../src/gcc-5666.3/fixincludes/fixincl.c:28:22: fatal error: sys/wait.h: No such file or directory [ERROR] make[3]: * [fixincl.o] Error 1 [ERROR] make[2]: * [all-build-fixincludes] Error 2 [ERROR] make[2]: * [all-fixincludes] Error 2 [38:33] -
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32030274 .
;) I'm going to rebuild my cygwined crosstools gcc4.8.2windows and gcc4.4.7linux to mingw, msys mingw seems much adapted for this than cygwin, had to slightly patch the official ctng to have it work on cygwin
This should be fixed now.
Oh, I committed the fix to crosstool-ng itself, and not as a patch in ctng-firefox-builds.
You should rm -rf crosstool-ng before running build.sh, or git pull --rebase it alternatively before issuing ./build.sh --target-os=osx
Thank you noticed that, I'm using tortoisesvn to always cleanup/revert and update before building anyway so I can apply my custom patch to the build.sh and I'm sure the code is latest version
For a general use with mingw32 to build the windows and linux toochains do you suggest me to keep using your build.sh script ? Because I wonder how a new user could discover your build.sh script ? Aren't you planning on upgrading your ct-ng fork to add a similar build script so the building under msys/mingw32 is more obvious
On Jan 12, 2014 2:59 AM, "Arnaud.Dovi" notifications@github.com wrote:
Thank you noticed that, I'm using tortoisesvn to cleanup/revert always before building anyway so I can apply my custom patch to the build.sh
OK. That's fine. I committed another fix for x86-64 two hours ago by the way so you way so you will need that. I hope that is the final fix needed. I will know soon enough if that is the case.
For a general use with mingw32 do you suggest me to keep using your build.sh script ? Because I wonder how a new user could discover your build.sh script ? aren't you planning on upgrading your ct-ng fork to add a similar build script so the building under msys/mingw32 is more obvious
Not sure what you mean by mingw32. I only support msys2 + mingw-w64 (which provides both 32 and 64 compilers somewhat confusingly). There is an old mingw project which I have no time for.
Well, ctng-firefox-builds is not strictly needed for Darwin. All the patches for that have been merged to this project already, it just makes things a bit easier to use by consolidating the important configuration options and hiding the irrelevant ones. It's also a testing ground for other hosts and targets and also (in some configurations) builds firefox with the cross compilers. One day soon it will die out and I will replace or with a set of sample configs for crosstool-ng. The hope is that finally this fork will be merged to the official crosstool-ng.
As for new users discovering it, it's not a script I'm hugely proud of - more an engineers tool - and while I am happy to help out when people discover this project or ctng-firefox-builds, it's not something I want to advertise hugely as if it were popular I would have to spend a lot of time supporting it I think.. It gets just the right level of interest at the minute :-)
— Reply to this email directly or view it on GitHub.
I didn't answer your question directly! Yes I recommend you stock with ctng-firefox-builds and build.sh On Jan 12, 2014 2:59 AM, "Arnaud.Dovi" notifications@github.com wrote:
Thank you noticed that, I'm using tortoisesvn to cleanup/revert always before building anyway so I can apply my custom patch to the build.sh
For a general use with mingw32 do you suggest me to keep using your build.sh script ? Because I wonder how a new user could discover your build.sh script ? aren't you planning on upgrading your ct-ng fork to add a similar build script so the building under msys/mingw32 is more obvious
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32113870 .
Quick update. It's getting further but there's something wrong still, this time I think a bug in cctools on Win64. For now, you should try to use 32bit MSYS2 while I look into it now:
http://sourceforge.net/projects/msys2/files/Base/i686/msys2-base-i686-20131208.tar.xz/download
On Sun, Jan 12, 2014 at 3:17 AM, Ray Donnelly mingw.android@gmail.comwrote:
I didn't answer your question directly! Yes I recommend you stock with ctng-firefox-builds and build.sh On Jan 12, 2014 2:59 AM, "Arnaud.Dovi" notifications@github.com wrote:
Thank you noticed that, I'm using tortoisesvn to cleanup/revert always before building anyway so I can apply my custom patch to the build.sh
For a general use with mingw32 do you suggest me to keep using your build.sh script ? Because I wonder how a new user could discover your build.sh script ? aren't you planning on upgrading your ct-ng fork to add a similar build script so the building under msys/mingw32 is more obvious
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32113870 .
Thank you I take note of this. I'm building yet for windows a seh x64 toolchain and sjlj 32 bit one (btw you can update your build.sh to use the rev2 of x86_64-4.8.2-release-win32-seh-rt_v3-rev2.7z, the sjlj one is at rev2 too.
Btw I also note when building a windows toolchain 32 or 64 bit with gdb set on default options (python/expat) it fails at finding expat, even after installing expat-devel and I attempted to copy the lib in various locations but no luck, was probably looking for the headers, i just disable python in the menuconfig and removing expat options from the build script does the trick
Well, you are right, I will disable debuggers until they work right (for now you can do ./build.sh --ctng-debuggers=no).
For Python, we need to pass to configure --with-python=/mingw64/bin/python-config.sh or --with-python=/mingw32/bin/python-config.sh, but in the long term I am considering adding Python to ctng.
In the meantime, I will commit a change to build.sh so that CTNG_DEBUGGERS is set to "default" and for Windows I will make that default be "no", I am also going to enable parallel make as it's so slow otherwise.
Expect this commit in the next 10 minutes.
On Sun, Jan 12, 2014 at 3:46 PM, Arnaud.Dovi notifications@github.comwrote:
Thank you I take note of this. I'm building yet for windows a seh x64 toolchain and sjlj 32 bit one (btw you can update your build.sh to use the rev2 of x86_64-4.8.2-release-win32-seh-rt_v3-rev2.7z
Btw I also note when building a windows toolchain 32 or 64 bit with gdb set on default options (python/expat) it fails at finding expat, even after installing expat-devel and I attempted to copy the lib in various locations but no luck, was probably looking for the headers, i just disable python in the menuconfig and removing expat options from the build script does the trick
— Reply to this email directly or view it on GitHubhttps://github.com/diorcety/crosstool-ng/issues/10#issuecomment-32125309 .
I'm stuck on this one, It seems on a cygwin host the cctools compilation targets i686-apple-darwin10 but with using the cygwin headers and gives this
Not sure yet the proper way to fix this, because if I include the 10.6 sdk includes and libraries files , seems to pass the compilation errors but then I'm stuck at many unresolved symbols to undefined reference to `fopen$UNIX2003' and more and gcc 4.8.2 cygwin can't seem to be able to link against the libSystem.B.dylib present in the sysroot/sdk folder
If you have any idea thank you.