Arnaud Dovi
Arnaud Dovi
You need to copy sdk to sysroot I have seen this size problem too while building a windows cross compiler targeting mac with clang 3.4, I think it comes from...
@inolen Btw if you want to get ride of the issue of llvm generated with an absurd size like 500MB+ for only LTO.dll making the final compiler ~1.5GB size, edit...
Addition: Btw I know you don't want to support ln -s but anyway to support it you should do instead ``` --- scripts/crosstool-NG.sh.in.orig 2014-02-03 22:10:11.752895600 +0100 +++ scripts/crosstool-NG.sh.in 2014-02-03 22:11:47.280186700...
this one not really required but this was when I was testing the non sysroot option, ${CT_PREFIX_DIR}/${CT_TARGET} = CT_SYSROOT_DIR and it was causing en error attempting to create the same...
btw I haven't scanned much = "n" but I haven't looked at case for example, maybe there are so case you look for a "n"
There is something strange when attempting to use them to compile helloworld c++ ``` #include using namespace std; main() { cout
``` Administrator@WIN81PRO /x/helloworld $ /x/libs/gcc-4.8.2-x86_64-w64-mingw32-seh/bin/x86_64-w64-mingw32-g++.exe -v Using built-in specs. COLLECT_GCC=X:\libs\gcc-4.8.2-x86_64-w64-mingw32-seh\bin\x86_64-w64-mingw32-g++.exe COLLECT_LTO_WRAPPER=X:/libs/gcc-4.8.2-x86_64-w64-mingw32-seh/libexec/gcc/x86_64-w64-mingw32/4.8.2/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: ../../../src/gcc-4.8.2/configure --build=x86_64-build_w64-mingw32 --host=x86_64-build_w64-mingw32 --target=x86_64-w64-mingw32 --prefix=/x/libs/gcc-4.8.2-x86_64-w64-mingw32-seh --with-sysroot=/x/libs/gcc-4.8.2-x86_64-w64-mingw32-seh/x86_64-w64-mingw32/sysroot --enable-languages=c,c++ --with-arch=x86-64 --enable-shared --enable-static --with-pkgversion='crosstool-NG hg+unknown-20140130.120229' --enable-__cxa_atexit --disable-libmudflap --disable-libgomp...
Wow set MSYS=winsymlinks:nativestrict is wonderful this is what I was looking for makes true links ! I think I'm going to rebuild with this
On Darwin I have just attempted yet to extract with msys tar the xz he mades but it was the same type of links just a filename inside the file...
I think I see when the bug happens, when it is building gcc final it fails and when I have used process monitor I realize it is looking for X:\libs\gcc-4.8.2-x86_64-unknown-linux-dw2\x86_64-unknown-linux-gnu\include...